Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a67ac200775e7233c340243da9996a8f8f4b1ffc3f5d170a03a9d230c7cf5ba2

Tx prefix hash: 73992035c9d90fb702dbc6f2e60fec5a34c0a83829743798a745fb816f7c903a
Tx public key: 8a8c912c8f4ba67df4cb4ecad6d98fd1f7d705a25d43222945ab2400fa2dc7a5
Timestamp: 1733645247 Timestamp [UCT]: 2024-12-08 08:07:27 Age [y:d:h:m:s]: 00:333:00:33:17
Block: 1170586 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235496 RingCT/type: yes/0
Extra: 018a8c912c8f4ba67df4cb4ecad6d98fd1f7d705a25d43222945ab2400fa2dc7a50211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3b2e531af32a808c226035e162d306628639163a48a946d823cfad8794d13b6e 0.600000000000 1656317 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": 1170596, "vin": [ { "gen": { "height": 1170586 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b2e531af32a808c226035e162d306628639163a48a946d823cfad8794d13b6e" } } ], "extra": [ 1, 138, 140, 145, 44, 143, 75, 166, 125, 244, 203, 78, 202, 214, 217, 143, 209, 247, 215, 5, 162, 93, 67, 34, 41, 69, 171, 36, 0, 250, 45, 199, 165, 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