Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f2ded8f9365e215e604df60f2412ccd60952c1fa65e8c2a26ce1ca82137a3db

Tx prefix hash: 3d7f240246066349b9244e4b4fd453c49a5c4f727dd94e3bc3fa95efb89014da
Tx public key: 05f047994191fa5dfc7db52c313c4a021e22aee53546f63e41f2d659691dc488
Timestamp: 1715028708 Timestamp [UCT]: 2024-05-06 20:51:48 Age [y:d:h:m:s]: 00:191:13:10:25
Block: 1016352 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 137103 RingCT/type: yes/0
Extra: 0105f047994191fa5dfc7db52c313c4a021e22aee53546f63e41f2d659691dc4880211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5d041bfef1df88b4d891cc782aedee2843eb8380c8806c85a25893e9e3505565 0.600000000000 1479907 of 15

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": 1016362, "vin": [ { "gen": { "height": 1016352 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d041bfef1df88b4d891cc782aedee2843eb8380c8806c85a25893e9e3505565" } } ], "extra": [ 1, 5, 240, 71, 153, 65, 145, 250, 93, 252, 125, 181, 44, 49, 60, 74, 2, 30, 34, 174, 229, 53, 70, 246, 62, 65, 242, 214, 89, 105, 29, 196, 136, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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