Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d558ceb9334b1f90e1264dd1e3a26376fbe809c4e1cb85eef157968670ab9b2e

Tx prefix hash: 010d93e04f2eaa4cc0d0b9463c367f000161fda909e5ba435f7bb9e3e6a7b7e7
Tx public key: 0a60f80d5111832f5bba2523e8115a5703d7a714ab166eef76006c6e6f62c6ed
Timestamp: 1749692875 Timestamp [UCT]: 2025-06-12 01:47:55 Age [y:d:h:m:s]: 00:155:02:58:03
Block: 1303141 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108571 RingCT/type: yes/0
Extra: 010a60f80d5111832f5bba2523e8115a5703d7a714ab166eef76006c6e6f62c6ed02110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f26a11a0c4e2fdfa93aa9e4cf134b5e2a0ea1b39b0131359eea6c5518f83b3d 0.600000000000 1790716 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": 1303151, "vin": [ { "gen": { "height": 1303141 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f26a11a0c4e2fdfa93aa9e4cf134b5e2a0ea1b39b0131359eea6c5518f83b3d" } } ], "extra": [ 1, 10, 96, 248, 13, 81, 17, 131, 47, 91, 186, 37, 35, 232, 17, 90, 87, 3, 215, 167, 20, 171, 22, 110, 239, 118, 0, 108, 110, 111, 98, 198, 237, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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