Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e3f2a1a438abb87b675c14af7eed445686d45b9b733db7686db32720f2011394

Tx prefix hash: aa8811ba23f724e2937314e5fca3c617ee6e0c3a0978e7e50b608b429ac28b23
Tx public key: c0f2e8b9a25ec3e76bb0fba92c3f95ce2acc344b34f7ed072bb31010c849a441
Timestamp: 1736529364 Timestamp [UCT]: 2025-01-10 17:16:04 Age [y:d:h:m:s]: 00:159:20:23:45
Block: 1194443 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113956 RingCT/type: yes/0
Extra: 01c0f2e8b9a25ec3e76bb0fba92c3f95ce2acc344b34f7ed072bb31010c849a4410211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8294580498c2aa6b14a67609e6ecb3d5d11316b8a646f787a4c77938cd4b755c 0.600000000000 1681014 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": 1194453, "vin": [ { "gen": { "height": 1194443 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8294580498c2aa6b14a67609e6ecb3d5d11316b8a646f787a4c77938cd4b755c" } } ], "extra": [ 1, 192, 242, 232, 185, 162, 94, 195, 231, 107, 176, 251, 169, 44, 63, 149, 206, 42, 204, 52, 75, 52, 247, 237, 7, 43, 179, 16, 16, 200, 73, 164, 65, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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