Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f09ce6c8995e33356e37cd452260dec0fd525d73a374101433b5c6b5f3cbea8

Tx prefix hash: b2d225a10d24c3f4236383ceb8c14f73f58046708a51df398dfc543d9175839e
Tx public key: 68533ea9404fa8550e1f3ef53977f0546cfe344c32d8b3aa40d4fb86cd3fc877
Timestamp: 1732477804 Timestamp [UCT]: 2024-11-24 19:50:04 Age [y:d:h:m:s]: 01:022:01:32:37
Block: 1160907 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 274206 RingCT/type: yes/0
Extra: 0168533ea9404fa8550e1f3ef53977f0546cfe344c32d8b3aa40d4fb86cd3fc877021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ef843a236f6b46867477dedca3c4ae0158186992b335cb6e803607c5f66272a7 0.600000000000 1646558 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": 1160917, "vin": [ { "gen": { "height": 1160907 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef843a236f6b46867477dedca3c4ae0158186992b335cb6e803607c5f66272a7" } } ], "extra": [ 1, 104, 83, 62, 169, 64, 79, 168, 85, 14, 31, 62, 245, 57, 119, 240, 84, 108, 254, 52, 76, 50, 216, 179, 170, 64, 212, 251, 134, 205, 63, 200, 119, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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