Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b86caed6f12f3059ebf49923631138a145bacbcc687cba62501caad6f13976e

Tx prefix hash: 5dc91e05af5659b1580c34a7b1e1c1bc4560ba862d932badcd26f3d674a7a550
Tx public key: 93eaaded0f9d66a0d27add4d57304a5ed11d8ae17cfdea4d9de99172d023cee2
Timestamp: 1741394102 Timestamp [UCT]: 2025-03-08 00:35:02 Age [y:d:h:m:s]: 00:211:00:05:36
Block: 1234464 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148485 RingCT/type: yes/0
Extra: 0193eaaded0f9d66a0d27add4d57304a5ed11d8ae17cfdea4d9de99172d023cee20211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: caafe6160839e43394a77a99de3c91db56881ca9d184d4316b03832d0fb7871a 0.600000000000 1721391 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": 1234474, "vin": [ { "gen": { "height": 1234464 } } ], "vout": [ { "amount": 600000000, "target": { "key": "caafe6160839e43394a77a99de3c91db56881ca9d184d4316b03832d0fb7871a" } } ], "extra": [ 1, 147, 234, 173, 237, 15, 157, 102, 160, 210, 122, 221, 77, 87, 48, 74, 94, 209, 29, 138, 225, 124, 253, 234, 77, 157, 233, 145, 114, 208, 35, 206, 226, 2, 17, 0, 0, 0, 1, 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