Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a52611cb0f55ac384a7d603b4d184229740d8bda97b626d9f2a4b795dd5ed133

Tx prefix hash: 88e65ba3c13dbf359d7efe148fd85401644e8efc7d5efbe2a4e77d9fa117e008
Tx public key: 92fa122c9c4bc8471f0cb4f94d1381c27c7c44d7fff1b4e56b008bacf59fef22
Timestamp: 1699464063 Timestamp [UCT]: 2023-11-08 17:21:03 Age [y:d:h:m:s]: 01:062:10:59:29
Block: 887310 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306040 RingCT/type: yes/0
Extra: 0192fa122c9c4bc8471f0cb4f94d1381c27c7c44d7fff1b4e56b008bacf59fef22021100000004faf35c9c000000000000000000

1 output(s) for total of 0.704650285000 dcy

stealth address amount amount idx
00: 5fcaf9708dc827b8441224dbf40fa7b574c0f0ef18f6aa48d11a29f73f48f1da 0.704650285000 1343181 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": 887320, "vin": [ { "gen": { "height": 887310 } } ], "vout": [ { "amount": 704650285, "target": { "key": "5fcaf9708dc827b8441224dbf40fa7b574c0f0ef18f6aa48d11a29f73f48f1da" } } ], "extra": [ 1, 146, 250, 18, 44, 156, 75, 200, 71, 31, 12, 180, 249, 77, 19, 129, 194, 124, 124, 68, 215, 255, 241, 180, 229, 107, 0, 139, 172, 245, 159, 239, 34, 2, 17, 0, 0, 0, 4, 250, 243, 92, 156, 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