Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4716bc02baa474610fcf09fcf35336e333cfc698c0d9410a3ca81eeca39379c

Tx prefix hash: cd8d3d405a87d50172e87a777b30f837aba196ede1146f2c6554494f9892f095
Tx public key: c3a32c14f96a518877d6dfcd0b74f9e5344dbb41ca71cb402f1dcf5a594961c9
Timestamp: 1695011958 Timestamp [UCT]: 2023-09-18 04:39:18 Age [y:d:h:m:s]: 01:205:07:08:28
Block: 850586 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 407807 RingCT/type: yes/0
Extra: 01c3a32c14f96a518877d6dfcd0b74f9e5344dbb41ca71cb402f1dcf5a594961c90211000000034b8f5122000000000000000000

1 output(s) for total of 0.932514391000 dcy

stealth address amount amount idx
00: f6886965035b4d40bca26db44062bebdab81d347f8823a58c483b7574fb1a806 0.932514391000 1304316 of 0

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": 850596, "vin": [ { "gen": { "height": 850586 } } ], "vout": [ { "amount": 932514391, "target": { "key": "f6886965035b4d40bca26db44062bebdab81d347f8823a58c483b7574fb1a806" } } ], "extra": [ 1, 195, 163, 44, 20, 249, 106, 81, 136, 119, 214, 223, 205, 11, 116, 249, 229, 52, 77, 187, 65, 202, 113, 203, 64, 47, 29, 207, 90, 89, 73, 97, 201, 2, 17, 0, 0, 0, 3, 75, 143, 81, 34, 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