Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01f4fee75c758f788dec306141a61fc4f2a120e1e80579ce80330aa8aed4d8fd

Tx prefix hash: e5d854c299d1c275b1fbbca208cc4fa314aa116abe5e8c029f6f77aa77756ac6
Tx public key: 0d05a3727021de158a93000b90d54b451d6fcde03c48ca633ff20aea8b9f1f94
Timestamp: 1747268602 Timestamp [UCT]: 2025-05-15 00:23:22 Age [y:d:h:m:s]: 00:146:19:34:46
Block: 1283100 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102565 RingCT/type: yes/0
Extra: 010d05a3727021de158a93000b90d54b451d6fcde03c48ca633ff20aea8b9f1f940211000000029f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ad252b33cabfb72c091524e484c815ce74d399d3c1519a79adcb0e00dd6e58e 0.600000000000 1770517 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": 1283110, "vin": [ { "gen": { "height": 1283100 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ad252b33cabfb72c091524e484c815ce74d399d3c1519a79adcb0e00dd6e58e" } } ], "extra": [ 1, 13, 5, 163, 114, 112, 33, 222, 21, 138, 147, 0, 11, 144, 213, 75, 69, 29, 111, 205, 224, 60, 72, 202, 99, 63, 242, 10, 234, 139, 159, 31, 148, 2, 17, 0, 0, 0, 2, 159, 159, 230, 140, 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