Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 54ac4af9b892e3e5b197e4cdfba2d453352748b76d66d9512830be90398a1347

Tx prefix hash: d2525cb5fc4b65056a3f642293bf1a9b4bf5bae9c1a62cd7591dc2690708bed6
Tx public key: a8f6a0c2a4f4458ebfc7d82b782104af4d3c3d9c0260f8f35243af06342d7ddf
Timestamp: 1699854745 Timestamp [UCT]: 2023-11-13 05:52:25 Age [y:d:h:m:s]: 01:065:06:07:26
Block: 890551 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308032 RingCT/type: yes/0
Extra: 01a8f6a0c2a4f4458ebfc7d82b782104af4d3c3d9c0260f8f35243af06342d7ddf02110000000475e3f0e9000000000000000000

1 output(s) for total of 0.687440079000 dcy

stealth address amount amount idx
00: ef8673060ad75df9b212c8772a7999bb264e933beed1c53f008e7544a1e358b2 0.687440079000 1346574 of 0

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": 890561, "vin": [ { "gen": { "height": 890551 } } ], "vout": [ { "amount": 687440079, "target": { "key": "ef8673060ad75df9b212c8772a7999bb264e933beed1c53f008e7544a1e358b2" } } ], "extra": [ 1, 168, 246, 160, 194, 164, 244, 69, 142, 191, 199, 216, 43, 120, 33, 4, 175, 77, 60, 61, 156, 2, 96, 248, 243, 82, 67, 175, 6, 52, 45, 125, 223, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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