Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b11d713286d647c7834249671a41f4c839e00e6d4f25d052bd343b9bfd52293f

Tx prefix hash: b38b1cf6cadfccb83968eaa732bbe63f5807b76aaba2fdad7ba1eeef182d79d4
Tx public key: 3e33fb09a40eaa1d4a10dd363978ce59b847154db48aa8badb190c216052c285
Timestamp: 1760903640 Timestamp [UCT]: 2025-10-19 19:54:00 Age [y:d:h:m:s]: 00:020:06:55:43
Block: 1393568 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 14502 RingCT/type: yes/0
Extra: 013e33fb09a40eaa1d4a10dd363978ce59b847154db48aa8badb190c216052c28502110000000825a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f42e632ec2caa9196f3cd263e10a363f3dabc5e5ae869c6e0f87180a14d43d06 0.600000000000 1881833 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": 1393578, "vin": [ { "gen": { "height": 1393568 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f42e632ec2caa9196f3cd263e10a363f3dabc5e5ae869c6e0f87180a14d43d06" } } ], "extra": [ 1, 62, 51, 251, 9, 164, 14, 170, 29, 74, 16, 221, 54, 57, 120, 206, 89, 184, 71, 21, 77, 180, 138, 168, 186, 219, 25, 12, 33, 96, 82, 194, 133, 2, 17, 0, 0, 0, 8, 37, 163, 90, 15, 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