Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed60b17c5f5fb6b2f1dd481e216deac06aa63a80f665c86186497ec9c3d13768

Tx prefix hash: cc7639ab67f90f9ff234d9541b52fdce75531f7d356ef8b203015d2ccf31789f
Tx public key: c12ce5d7f30c5e3f4b68bc60b0357abec5202a80870d55472b3acec01629e450
Timestamp: 1738262512 Timestamp [UCT]: 2025-01-30 18:41:52 Age [y:d:h:m:s]: 00:292:19:26:41
Block: 1208538 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207032 RingCT/type: yes/0
Extra: 01c12ce5d7f30c5e3f4b68bc60b0357abec5202a80870d55472b3acec01629e450021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ff7c78a728fa58894a740bef812bae97f2f46d3f63f19c43b270c8af031c2657 0.600000000000 1695271 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": 1208548, "vin": [ { "gen": { "height": 1208538 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ff7c78a728fa58894a740bef812bae97f2f46d3f63f19c43b270c8af031c2657" } } ], "extra": [ 1, 193, 44, 229, 215, 243, 12, 94, 63, 75, 104, 188, 96, 176, 53, 122, 190, 197, 32, 42, 128, 135, 13, 85, 71, 43, 58, 206, 192, 22, 41, 228, 80, 2, 17, 0, 0, 0, 3, 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