Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2eb02e24c759f304d961b647a9bc1f1349fa5208104e21b1606c3a15233428a

Tx prefix hash: 0869918af632852bba22cb319568b0bed1b77c84c2538cc116cb45c318bdca79
Tx public key: 24e05c299b7e1026a89198741ed04e1c1493adf82402c56bcc613b762a8a7d4e
Timestamp: 1703974847 Timestamp [UCT]: 2023-12-30 22:20:47 Age [y:d:h:m:s]: 01:093:21:25:51
Block: 924696 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 328207 RingCT/type: yes/0
Extra: 0124e05c299b7e1026a89198741ed04e1c1493adf82402c56bcc613b762a8a7d4e0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5c57335a3a1d031a290defa0ef78b6dd5d9794ee6e5c65a0d45b0b002e0ee1ca 0.600000000000 1382452 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": 924706, "vin": [ { "gen": { "height": 924696 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c57335a3a1d031a290defa0ef78b6dd5d9794ee6e5c65a0d45b0b002e0ee1ca" } } ], "extra": [ 1, 36, 224, 92, 41, 155, 126, 16, 38, 168, 145, 152, 116, 30, 208, 78, 28, 20, 147, 173, 248, 36, 2, 197, 107, 204, 97, 59, 118, 42, 138, 125, 78, 2, 17, 0, 0, 0, 1, 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