Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c230a932fd0082b311e12eb79e9afb4063dfd45ca33ae526e254c14b3b904902

Tx prefix hash: 0303172e1c6e1a496d4aea6e74a12b2e5393ff71fac225f8154f47cef49ab802
Tx public key: 915e2534587551cda8a70ff280e6aaf60b941370a14868205055ee2ecf4a993a
Timestamp: 1714474303 Timestamp [UCT]: 2024-04-30 10:51:43 Age [y:d:h:m:s]: 00:332:03:49:42
Block: 1011741 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237447 RingCT/type: yes/0
Extra: 01915e2534587551cda8a70ff280e6aaf60b941370a14868205055ee2ecf4a993a0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 032d7dab329de23eca614df7f61bbb624eeb19e5df2b14e77b9fa4f272adea15 0.600000000000 1474049 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": 1011751, "vin": [ { "gen": { "height": 1011741 } } ], "vout": [ { "amount": 600000000, "target": { "key": "032d7dab329de23eca614df7f61bbb624eeb19e5df2b14e77b9fa4f272adea15" } } ], "extra": [ 1, 145, 94, 37, 52, 88, 117, 81, 205, 168, 167, 15, 242, 128, 230, 170, 246, 11, 148, 19, 112, 161, 72, 104, 32, 80, 85, 238, 46, 207, 74, 153, 58, 2, 17, 0, 0, 0, 5, 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