Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6e249da251d43a82118552e95e180d8d4016b1f85d75983837f4af07c4490f9

Tx prefix hash: 5e96a1a77db5a384508a378b27f0114db46a8e8338a8aac77232ef8745698b56
Tx public key: 49ef1d24754d348981f4ca04f92c7acc355c49401a55267a5b3b4fcd5a0b82a6
Timestamp: 1762943840 Timestamp [UCT]: 2025-11-12 10:37:20 Age [y:d:h:m:s]: 00:081:02:35:08
Block: 1410450 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 57893 RingCT/type: yes/0
Extra: 0149ef1d24754d348981f4ca04f92c7acc355c49401a55267a5b3b4fcd5a0b82a60211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b3cc8570991d55bef9ae47fe569f0d6d82584a2e36af610288012230d5e0a3b 0.600000000000 1898901 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": 1410460, "vin": [ { "gen": { "height": 1410450 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b3cc8570991d55bef9ae47fe569f0d6d82584a2e36af610288012230d5e0a3b" } } ], "extra": [ 1, 73, 239, 29, 36, 117, 77, 52, 137, 129, 244, 202, 4, 249, 44, 122, 204, 53, 92, 73, 64, 26, 85, 38, 122, 91, 59, 79, 205, 90, 11, 130, 166, 2, 17, 0, 0, 0, 3, 38, 9, 179, 160, 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