Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: caf98a2be2ea91de1b4365d76ee294c799518d1d7eec528124aa471e59c185eb

Tx prefix hash: 13faa1850255b3fdf20471bdf439d7881383f32819fa98cc4afd9ec98d9bc1fc
Tx public key: e5d0a33ca3e5301f0f83cd37bdc6c3377e1009659a0dac7c48c321e3b618aa72
Timestamp: 1753541498 Timestamp [UCT]: 2025-07-26 14:51:38 Age [y:d:h:m:s]: 00:030:05:28:35
Block: 1333859 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 20496 RingCT/type: yes/0
Extra: 01e5d0a33ca3e5301f0f83cd37bdc6c3377e1009659a0dac7c48c321e3b618aa72021100000005ef221485000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 193a56dec51310fd7a0ca3e15fd4ee729e959046ee44296ad63443d71e10d79c 0.600000000000 1821658 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": 1333869, "vin": [ { "gen": { "height": 1333859 } } ], "vout": [ { "amount": 600000000, "target": { "key": "193a56dec51310fd7a0ca3e15fd4ee729e959046ee44296ad63443d71e10d79c" } } ], "extra": [ 1, 229, 208, 163, 60, 163, 229, 48, 31, 15, 131, 205, 55, 189, 198, 195, 55, 126, 16, 9, 101, 154, 13, 172, 124, 72, 195, 33, 227, 182, 24, 170, 114, 2, 17, 0, 0, 0, 5, 239, 34, 20, 133, 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