Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 78446f4edc0ed61292bc7144a097f7c28b454aa7877f593dbd6c7386d62d3f8b

Tx prefix hash: 65c4b1b6eb17f49565b0e7f7c07984c7b925ecfa3a654fa442bbc277fe61ee7d
Tx public key: c49c3421d6ef81a65077ccc80f2f89d2f6de97ce5584426509f8c4bc82ce07c7
Timestamp: 1761971528 Timestamp [UCT]: 2025-11-01 04:32:08 Age [y:d:h:m:s]: 00:004:11:10:10
Block: 1402406 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3184 RingCT/type: yes/0
Extra: 01c49c3421d6ef81a65077ccc80f2f89d2f6de97ce5584426509f8c4bc82ce07c702110000000f5dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7e698aca3389b51c529ade08e8830d91ba93ef9083a4f64a71bee75e7e325aa6 0.600000000000 1890725 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": 1402416, "vin": [ { "gen": { "height": 1402406 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e698aca3389b51c529ade08e8830d91ba93ef9083a4f64a71bee75e7e325aa6" } } ], "extra": [ 1, 196, 156, 52, 33, 214, 239, 129, 166, 80, 119, 204, 200, 15, 47, 137, 210, 246, 222, 151, 206, 85, 132, 66, 101, 9, 248, 196, 188, 130, 206, 7, 199, 2, 17, 0, 0, 0, 15, 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