Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 31860e30b527a0b6bf51cba2ff82e2ccd41548aff5416d2e0f80c7d4e7c39f3f

Tx prefix hash: bf3df156824739b767394364c54773346b5cb73d94d0cbfde1371a2e939af853
Tx public key: 477d7f9f74d97bc4cf93918991071e027bd3847cf86c4d63dfc74849cf2b2631
Timestamp: 1693663712 Timestamp [UCT]: 2023-09-02 14:08:32 Age [y:d:h:m:s]: 01:239:06:45:12
Block: 839391 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 432159 RingCT/type: yes/0
Extra: 01477d7f9f74d97bc4cf93918991071e027bd3847cf86c4d63dfc74849cf2b2631021100000009e6d27f9c000000000000000000

1 output(s) for total of 1.015662087000 dcy

stealth address amount amount idx
00: e8c2d8f4b320afeb661a151fc6aa35d96a301a25361331529f13fa33642d1deb 1.015662087000 1292241 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 839401, "vin": [ { "gen": { "height": 839391 } } ], "vout": [ { "amount": 1015662087, "target": { "key": "e8c2d8f4b320afeb661a151fc6aa35d96a301a25361331529f13fa33642d1deb" } } ], "extra": [ 1, 71, 125, 127, 159, 116, 217, 123, 196, 207, 147, 145, 137, 145, 7, 30, 2, 123, 211, 132, 124, 248, 108, 77, 99, 223, 199, 72, 73, 207, 43, 38, 49, 2, 17, 0, 0, 0, 9, 230, 210, 127, 156, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8