Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 233b46ffaddf1cbbd3777fd34136babbc6f5ed3ab0b5714dbacc37cf4571bffb

Tx prefix hash: cd01ad25b4436ee1abe0b8566c5eb5b0602d7c28a3dd33ad575437f49239e6e9
Tx public key: 00e62fa91d778b6b8a3bde927a1c50c6af8e4eb160a86d310bb4f6cd430c2b68
Timestamp: 1734123761 Timestamp [UCT]: 2024-12-13 21:02:41 Age [y:d:h:m:s]: 00:111:13:42:02
Block: 1174547 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79524 RingCT/type: yes/0
Extra: 0100e62fa91d778b6b8a3bde927a1c50c6af8e4eb160a86d310bb4f6cd430c2b680211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 635e51633119fc23d79e26ebc08d0127cdcb5e24263cdd557550d46ee1482edc 0.600000000000 1660712 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": 1174557, "vin": [ { "gen": { "height": 1174547 } } ], "vout": [ { "amount": 600000000, "target": { "key": "635e51633119fc23d79e26ebc08d0127cdcb5e24263cdd557550d46ee1482edc" } } ], "extra": [ 1, 0, 230, 47, 169, 29, 119, 139, 107, 138, 59, 222, 146, 122, 28, 80, 198, 175, 142, 78, 177, 96, 168, 109, 49, 11, 180, 246, 205, 67, 12, 43, 104, 2, 17, 0, 0, 0, 2, 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