Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e20fd77ada3f0c4a6f5acebee7d30cf7834b66eb430ee21bef8581b93f65df2d

Tx prefix hash: 5064ed41224b52c8c78eadd7b04ab61153465eda48c14162d2c603e2299f0f67
Tx public key: 244f8ad90ec55861f3a237fbd613f6de5759176e72e875abe67b8e2f4f29fa30
Timestamp: 1765953497 Timestamp [UCT]: 2025-12-17 06:38:17 Age [y:d:h:m:s]: 00:004:05:03:54
Block: 1435391 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3017 RingCT/type: yes/0
Extra: 01244f8ad90ec55861f3a237fbd613f6de5759176e72e875abe67b8e2f4f29fa300211000000017b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 26f2b8050dd2cbef578fbf0d9774c6e18d22e8b812ecb1622d376eafddf30c4b 0.600000000000 1924188 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": 1435401, "vin": [ { "gen": { "height": 1435391 } } ], "vout": [ { "amount": 600000000, "target": { "key": "26f2b8050dd2cbef578fbf0d9774c6e18d22e8b812ecb1622d376eafddf30c4b" } } ], "extra": [ 1, 36, 79, 138, 217, 14, 197, 88, 97, 243, 162, 55, 251, 214, 19, 246, 222, 87, 89, 23, 110, 114, 232, 117, 171, 230, 123, 142, 47, 79, 41, 250, 48, 2, 17, 0, 0, 0, 1, 123, 30, 81, 172, 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