Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e86a93868942bd4c359bb2d3c673acd51c0cdd848f0934ae1ce13e167a03aec3

Tx prefix hash: 9899522ae0d230f8aa163a8b274511100c33d8a6983568c5938210a96a009250
Tx public key: 4783ff3baba1521ef1b7aaaf6d12eb4390d6e891440125d8b01f5d925baae225
Timestamp: 1731762274 Timestamp [UCT]: 2024-11-16 13:04:34 Age [y:d:h:m:s]: 00:358:06:36:19
Block: 1154985 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 253598 RingCT/type: yes/0
Extra: 014783ff3baba1521ef1b7aaaf6d12eb4390d6e891440125d8b01f5d925baae22502110000000b1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 74ce9f897d833aac2519d4ff79a2da5979e8fb5f45035d14876e1fb7378ea9c7 0.600000000000 1640598 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": 1154995, "vin": [ { "gen": { "height": 1154985 } } ], "vout": [ { "amount": 600000000, "target": { "key": "74ce9f897d833aac2519d4ff79a2da5979e8fb5f45035d14876e1fb7378ea9c7" } } ], "extra": [ 1, 71, 131, 255, 59, 171, 161, 82, 30, 241, 183, 170, 175, 109, 18, 235, 67, 144, 214, 232, 145, 68, 1, 37, 216, 176, 31, 93, 146, 91, 170, 226, 37, 2, 17, 0, 0, 0, 11, 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