Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 569dc6dfd03801c9c63e85f699e084fc7243188fbb01c52cd0a69a93d66b7b5d

Tx prefix hash: 95f7e2908075db9e7e349af736107e595ec77bca07cef2ab639a226fd4f92bcd
Tx public key: b4e3d9e99a158fac9ed294139b9174509c78a8ad249f880c0eff240e12d959db
Timestamp: 1762148801 Timestamp [UCT]: 2025-11-03 05:46:41 Age [y:d:h:m:s]: 00:054:17:08:22
Block: 1403851 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 39196 RingCT/type: yes/0
Extra: 01b4e3d9e99a158fac9ed294139b9174509c78a8ad249f880c0eff240e12d959db0211000000045dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b6d21fd75594b633f3bd8e0fb00b48e7219b905f5b2b68d6f893f7245543ced5 0.600000000000 1892204 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": 1403861, "vin": [ { "gen": { "height": 1403851 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b6d21fd75594b633f3bd8e0fb00b48e7219b905f5b2b68d6f893f7245543ced5" } } ], "extra": [ 1, 180, 227, 217, 233, 154, 21, 143, 172, 158, 210, 148, 19, 155, 145, 116, 80, 156, 120, 168, 173, 36, 159, 136, 12, 14, 255, 36, 14, 18, 217, 89, 219, 2, 17, 0, 0, 0, 4, 93, 251, 190, 42, 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