Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 547db24ea50f3d18ec630b9916d95a28940ce9eb2e52c72928fc995f15cf678a

Tx prefix hash: e2ed6025ee0914e24ee7fa2b89423685b363e79ffdb6f59d3f9cb42b65e61be8
Tx public key: 549ac8b1fee4a67b53fd935a40a076ef7a3566bda10605a924f23714c76d6d0c
Timestamp: 1761302634 Timestamp [UCT]: 2025-10-24 10:43:54 Age [y:d:h:m:s]: 00:017:10:50:28
Block: 1396867 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 12484 RingCT/type: yes/0
Extra: 01549ac8b1fee4a67b53fd935a40a076ef7a3566bda10605a924f23714c76d6d0c0211000000015dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3709af06b7f65ba9579f5d7c90f85f1febd1eaecfb43c24879b551f51e6fbacd 0.600000000000 1885154 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": 1396877, "vin": [ { "gen": { "height": 1396867 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3709af06b7f65ba9579f5d7c90f85f1febd1eaecfb43c24879b551f51e6fbacd" } } ], "extra": [ 1, 84, 154, 200, 177, 254, 228, 166, 123, 83, 253, 147, 90, 64, 160, 118, 239, 122, 53, 102, 189, 161, 6, 5, 169, 36, 242, 55, 20, 199, 109, 109, 12, 2, 17, 0, 0, 0, 1, 93, 251, 190, 42, 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