Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b7de31fc4eb94456b57e772e29a59faa0f2dd03d61d61c9b75111d0f5c2630d

Tx prefix hash: 6e31b740e91ec03d3a7d82499d4816d1a2752fec965e9caf1a8d95770620f528
Tx public key: 3ff2a3846a64c0fef64b454e1034f8e2ee6dd9ce1eb75d45af310541ae107dfa
Timestamp: 1721731852 Timestamp [UCT]: 2024-07-23 10:50:52 Age [y:d:h:m:s]: 00:256:03:58:26
Block: 1071905 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183002 RingCT/type: yes/0
Extra: 013ff2a3846a64c0fef64b454e1034f8e2ee6dd9ce1eb75d45af310541ae107dfa021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 448a925a869ba13f83e7a893135eeb163abe58603691d3efb74f9a1344df3b21 0.600000000000 1544302 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": 1071915, "vin": [ { "gen": { "height": 1071905 } } ], "vout": [ { "amount": 600000000, "target": { "key": "448a925a869ba13f83e7a893135eeb163abe58603691d3efb74f9a1344df3b21" } } ], "extra": [ 1, 63, 242, 163, 132, 106, 100, 192, 254, 246, 75, 69, 78, 16, 52, 248, 226, 238, 109, 217, 206, 30, 183, 93, 69, 175, 49, 5, 65, 174, 16, 125, 250, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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