Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9c54605946893d3e398ff00f373fdf7fd7a745c4564524f6ba6a5dce18c0f864

Tx prefix hash: 5d0f0698b44b6c2fdf688f04a207ba7795a08e7bcca81077a35752546a8a2bbd
Tx public key: 33045d2a833a12185d600bad3c45e94272540061d1115b23d4f2be8787f23df2
Timestamp: 1715076729 Timestamp [UCT]: 2024-05-07 10:12:09 Age [y:d:h:m:s]: 00:335:03:46:02
Block: 1016747 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 239561 RingCT/type: yes/0
Extra: 0133045d2a833a12185d600bad3c45e94272540061d1115b23d4f2be8787f23df202110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b829c584fd08cce5ae9cd978f82fa199f83214ab9bf826fbefb684dbf66ebf7b 0.600000000000 1480416 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": 1016757, "vin": [ { "gen": { "height": 1016747 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b829c584fd08cce5ae9cd978f82fa199f83214ab9bf826fbefb684dbf66ebf7b" } } ], "extra": [ 1, 51, 4, 93, 42, 131, 58, 18, 24, 93, 96, 11, 173, 60, 69, 233, 66, 114, 84, 0, 97, 209, 17, 91, 35, 212, 242, 190, 135, 135, 242, 61, 242, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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