Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 67344feb726146ab71e1354b09afde44b4e2e48fbd6dd57b9602cd53225d3634

Tx prefix hash: 59a3cda1f1b3c948da93bd43189df207e00e5b14e759264d8e5d555c92705c93
Tx public key: 5a1e3dd8e9b9adb15156ac0ae9f8eff32ad0d33457ff3d929865422370ace6df
Timestamp: 1747548035 Timestamp [UCT]: 2025-05-18 06:00:35 Age [y:d:h:m:s]: 00:143:21:36:41
Block: 1285406 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100497 RingCT/type: yes/0
Extra: 015a1e3dd8e9b9adb15156ac0ae9f8eff32ad0d33457ff3d929865422370ace6df0211000000061f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 418b6056fd0b899f876a848a214d142e797fc7feb5ed03a72ee8bc92427f7f1d 0.600000000000 1772871 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": 1285416, "vin": [ { "gen": { "height": 1285406 } } ], "vout": [ { "amount": 600000000, "target": { "key": "418b6056fd0b899f876a848a214d142e797fc7feb5ed03a72ee8bc92427f7f1d" } } ], "extra": [ 1, 90, 30, 61, 216, 233, 185, 173, 177, 81, 86, 172, 10, 233, 248, 239, 243, 42, 208, 211, 52, 87, 255, 61, 146, 152, 101, 66, 35, 112, 172, 230, 223, 2, 17, 0, 0, 0, 6, 31, 144, 81, 122, 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