Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac8d12c432ff03bb54bdd7da45cc872958a768c0183a4c48f5d2be618180ae79

Tx prefix hash: edd052f679a2f002f271c542864f1a26070d26b3e22dc4d2824f7e6a9324812d
Tx public key: 4d3fffe7d080bd60bc3e275363200b93407e915116e592ce925847903b089c32
Timestamp: 1714329971 Timestamp [UCT]: 2024-04-28 18:46:11 Age [y:d:h:m:s]: 01:026:05:41:29
Block: 1010537 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 279720 RingCT/type: yes/0
Extra: 014d3fffe7d080bd60bc3e275363200b93407e915116e592ce925847903b089c3202110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ee13a5f3d39e9e0941a239f8c9ae01fb301afb9a33e8b90a6f4343d70f556064 0.600000000000 1472523 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": 1010547, "vin": [ { "gen": { "height": 1010537 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee13a5f3d39e9e0941a239f8c9ae01fb301afb9a33e8b90a6f4343d70f556064" } } ], "extra": [ 1, 77, 63, 255, 231, 208, 128, 189, 96, 188, 62, 39, 83, 99, 32, 11, 147, 64, 126, 145, 81, 22, 229, 146, 206, 146, 88, 71, 144, 59, 8, 156, 50, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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