Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 541486e20f8ec4fc6bfaa91485df4a36ed14fc643d58c3a380f8019a99fb98d1

Tx prefix hash: 93650ea45fd19b6d7fee9c9589932fa0a91ce9c5a642fc36c0999fd29578f49e
Tx public key: 60bca30a909901429f560306e7fa0e21c557fd04bee057226cb14f09141b49d5
Timestamp: 1760889144 Timestamp [UCT]: 2025-10-19 15:52:24 Age [y:d:h:m:s]: 00:033:00:04:01
Block: 1393449 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 23594 RingCT/type: yes/0
Extra: 0160bca30a909901429f560306e7fa0e21c557fd04bee057226cb14f09141b49d5021100000003e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e08c5fe6f625aa6878a9e080c67480a36fc0b5bbd6b96e447b8dbe356b98b345 0.600000000000 1881714 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": 1393459, "vin": [ { "gen": { "height": 1393449 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e08c5fe6f625aa6878a9e080c67480a36fc0b5bbd6b96e447b8dbe356b98b345" } } ], "extra": [ 1, 96, 188, 163, 10, 144, 153, 1, 66, 159, 86, 3, 6, 231, 250, 14, 33, 197, 87, 253, 4, 190, 224, 87, 34, 108, 177, 79, 9, 20, 27, 73, 213, 2, 17, 0, 0, 0, 3, 228, 220, 144, 9, 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