Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0df8570dc95959eaddc3a8ca3bebfe3314b0b3dfa4f7c8fceee3e6e896229dad

Tx prefix hash: 9e2b9af9da873785407fd108e2a5ab7fa6ead4fbf31c8f37319f75c62d3403e6
Tx public key: 80eb5c7f4e39a5a0fe5116dc489417aabe46c627511e1d8e359fd47c803862f6
Timestamp: 1698373003 Timestamp [UCT]: 2023-10-27 02:16:43 Age [y:d:h:m:s]: 01:089:02:59:27
Block: 878469 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 324879 RingCT/type: yes/0
Extra: 0180eb5c7f4e39a5a0fe5116dc489417aabe46c627511e1d8e359fd47c803862f6021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.753819813000 dcy

stealth address amount amount idx
00: 5ca69c09b07789d2cf1dcfe77d818251d56c8eac1de06720bc874cd09078c82d 0.753819813000 1333917 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": 878479, "vin": [ { "gen": { "height": 878469 } } ], "vout": [ { "amount": 753819813, "target": { "key": "5ca69c09b07789d2cf1dcfe77d818251d56c8eac1de06720bc874cd09078c82d" } } ], "extra": [ 1, 128, 235, 92, 127, 78, 57, 165, 160, 254, 81, 22, 220, 72, 148, 23, 170, 190, 70, 198, 39, 81, 30, 29, 142, 53, 159, 212, 124, 128, 56, 98, 246, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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