Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c20685f67affcc8cf7de1e69fe8edff28b90532445c79882b7aa219382a6577c

Tx prefix hash: e1ce0989a2d4d6fb66a336783d52004d8f5c69966cd90652e00683125ae118ed
Tx public key: 167d1a47ca8d98a1a7ce618c28919a55e7d627e9f9adcfa13b9979105b07559b
Timestamp: 1757143087 Timestamp [UCT]: 2025-09-06 07:18:07 Age [y:d:h:m:s]: 00:148:04:57:31
Block: 1362471 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105843 RingCT/type: yes/0
Extra: 01167d1a47ca8d98a1a7ce618c28919a55e7d627e9f9adcfa13b9979105b07559b02110000000cad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 300acba8b8a3a21160fef39063c6c3855c4bcebf4eea0b18a346f1598e67d152 0.600000000000 1850502 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": 1362481, "vin": [ { "gen": { "height": 1362471 } } ], "vout": [ { "amount": 600000000, "target": { "key": "300acba8b8a3a21160fef39063c6c3855c4bcebf4eea0b18a346f1598e67d152" } } ], "extra": [ 1, 22, 125, 26, 71, 202, 141, 152, 161, 167, 206, 97, 140, 40, 145, 154, 85, 231, 214, 39, 233, 249, 173, 207, 161, 59, 153, 121, 16, 91, 7, 85, 155, 2, 17, 0, 0, 0, 12, 173, 121, 72, 208, 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