Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0dc4fd71b5b5f2c872abc1aa7e10c13553373ad1b5464cfd4675a436cc8a358b

Tx prefix hash: 527fb8eead5bf1a6177ab6f8c6f5f28b828c38864c91222dcc7e8ad7abd8ad88
Tx public key: 43aa2700b9fdabe4356ff0f3f95202492e0703a2aef8f10528c8ad6fbc6661e4
Timestamp: 1738242164 Timestamp [UCT]: 2025-01-30 13:02:44 Age [y:d:h:m:s]: 00:042:05:00:53
Block: 1208365 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 30207 RingCT/type: yes/0
Extra: 0143aa2700b9fdabe4356ff0f3f95202492e0703a2aef8f10528c8ad6fbc6661e4021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 88f560a7d0ce25ab66172366bc28b3312639e848b46f1d070efbc91697ad1a1e 0.600000000000 1695096 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": 1208375, "vin": [ { "gen": { "height": 1208365 } } ], "vout": [ { "amount": 600000000, "target": { "key": "88f560a7d0ce25ab66172366bc28b3312639e848b46f1d070efbc91697ad1a1e" } } ], "extra": [ 1, 67, 170, 39, 0, 185, 253, 171, 228, 53, 111, 240, 243, 249, 82, 2, 73, 46, 7, 3, 162, 174, 248, 241, 5, 40, 200, 173, 111, 188, 102, 97, 228, 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