Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 29fc2cc1db6dc477916790bcc0f2eda6c0d728fc7d947eb96b11a3d2aa8b6941

Tx prefix hash: d45e7593025343802bcf116f603740c54ded8ff81106925335c7107a9f5fd0e7
Tx public key: 8fbb2d5522499f417a37a2106ac5af2d8c73d6f3ba08e4ebed220754a927d833
Timestamp: 1706290013 Timestamp [UCT]: 2024-01-26 17:26:53 Age [y:d:h:m:s]: 01:063:21:12:06
Block: 943866 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306743 RingCT/type: yes/0
Extra: 018fbb2d5522499f417a37a2106ac5af2d8c73d6f3ba08e4ebed220754a927d83302110000000f0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e34742bb183ac58456293d222fdcd9ecfe712a5ac41ac39ae27042f581d2b33b 0.600000000000 1402092 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": 943876, "vin": [ { "gen": { "height": 943866 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e34742bb183ac58456293d222fdcd9ecfe712a5ac41ac39ae27042f581d2b33b" } } ], "extra": [ 1, 143, 187, 45, 85, 34, 73, 159, 65, 122, 55, 162, 16, 106, 197, 175, 45, 140, 115, 214, 243, 186, 8, 228, 235, 237, 34, 7, 84, 169, 39, 216, 51, 2, 17, 0, 0, 0, 15, 0, 17, 5, 91, 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