Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0673a536916b2bb8ceb1b291703cce0a71b5cc9216acdc42e4570f32d9984269

Tx prefix hash: 07064700432dffd692726fa69f44f8178862a8cba1005a7ae9d275900685dda3
Tx public key: 8c8472f330eff9f8c5e6845a8b22b0df4f22e94896d4412b76abe103a3ec409e
Timestamp: 1735244364 Timestamp [UCT]: 2024-12-26 20:19:24 Age [y:d:h:m:s]: 00:092:10:51:15
Block: 1183814 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 65857 RingCT/type: yes/0
Extra: 018c8472f330eff9f8c5e6845a8b22b0df4f22e94896d4412b76abe103a3ec409e0211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7d9efa4b11e1965e16a51a3fd303aea78bb80e24502e343289a31e4c492371b6 0.600000000000 1670263 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": 1183824, "vin": [ { "gen": { "height": 1183814 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7d9efa4b11e1965e16a51a3fd303aea78bb80e24502e343289a31e4c492371b6" } } ], "extra": [ 1, 140, 132, 114, 243, 48, 239, 249, 248, 197, 230, 132, 90, 139, 34, 176, 223, 79, 34, 233, 72, 150, 212, 65, 43, 118, 171, 225, 3, 163, 236, 64, 158, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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