Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d43dcb5867ca23b3c24c6510f69dbe85011b3dc0b82fc2c24624762efab8a244

Tx prefix hash: 4cffd805034e2a852e4c3494556fb63b07348705573ff1f79a2afd0e6f91e0f9
Tx public key: 8eda512b1c38be82fafff37edb7eb3d0c40e95ed7e9b09f279388d39cd4a3565
Timestamp: 1764708749 Timestamp [UCT]: 2025-12-02 20:52:29 Age [y:d:h:m:s]: 00:001:05:55:32
Block: 1425086 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 886 RingCT/type: yes/0
Extra: 018eda512b1c38be82fafff37edb7eb3d0c40e95ed7e9b09f279388d39cd4a356502110000000517b19132000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 06b58b31acd774cc1de19dc9082c70995ce05733b276d6e90ab4c2d9a128374b 0.600000000000 1913719 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": 1425096, "vin": [ { "gen": { "height": 1425086 } } ], "vout": [ { "amount": 600000000, "target": { "key": "06b58b31acd774cc1de19dc9082c70995ce05733b276d6e90ab4c2d9a128374b" } } ], "extra": [ 1, 142, 218, 81, 43, 28, 56, 190, 130, 250, 255, 243, 126, 219, 126, 179, 208, 196, 14, 149, 237, 126, 155, 9, 242, 121, 56, 141, 57, 205, 74, 53, 101, 2, 17, 0, 0, 0, 5, 23, 177, 145, 50, 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