Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db4dd6c072a054f1110bfe5a65f87eb7009a9fc23d273d42a76e1372225c6827

Tx prefix hash: 5c5e338a2baa20e1a66484987ba2ec6b1a4406e16ba32f8c15a52070fae3c441
Tx public key: 25e5af74c3b43d6415b85cfed184f47236db2458174e8bed623ed909b7809bf3
Timestamp: 1706625140 Timestamp [UCT]: 2024-01-30 14:32:20 Age [y:d:h:m:s]: 01:282:00:04:34
Block: 946650 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 460343 RingCT/type: yes/0
Extra: 0125e5af74c3b43d6415b85cfed184f47236db2458174e8bed623ed909b7809bf302110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 807e45fd812df8d883066b34ae81779ce3e57d03e31ea7ec7c3b18d30e32df50 0.600000000000 1404984 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": 946660, "vin": [ { "gen": { "height": 946650 } } ], "vout": [ { "amount": 600000000, "target": { "key": "807e45fd812df8d883066b34ae81779ce3e57d03e31ea7ec7c3b18d30e32df50" } } ], "extra": [ 1, 37, 229, 175, 116, 195, 180, 61, 100, 21, 184, 92, 254, 209, 132, 244, 114, 54, 219, 36, 88, 23, 78, 139, 237, 98, 62, 217, 9, 183, 128, 155, 243, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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