Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d1edc7a17950c88ced98f6310eb76f1b01cb203a483fae5da420302fba54e40c

Tx prefix hash: c95be0d3c543ed786431583fdebd55c1e9260b6910dd9ff26c7dbd96ef403a53
Tx public key: 622ae6f48057a44bf6bc0957fbaa1c01c6cbd150f6d9d425d5a1ecf2a3802585
Timestamp: 1737606251 Timestamp [UCT]: 2025-01-23 04:24:11 Age [y:d:h:m:s]: 00:150:20:39:32
Block: 1203326 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107480 RingCT/type: yes/0
Extra: 01622ae6f48057a44bf6bc0957fbaa1c01c6cbd150f6d9d425d5a1ecf2a3802585021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d29b7664cbdee5b576efb70bf82fd777190dcf1a7effcaaf1c7442f396f26edf 0.600000000000 1690001 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": 1203336, "vin": [ { "gen": { "height": 1203326 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d29b7664cbdee5b576efb70bf82fd777190dcf1a7effcaaf1c7442f396f26edf" } } ], "extra": [ 1, 98, 42, 230, 244, 128, 87, 164, 75, 246, 188, 9, 87, 251, 170, 28, 1, 198, 203, 209, 80, 246, 217, 212, 37, 213, 161, 236, 242, 163, 128, 37, 133, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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