Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c6fb5b5c7081a488f19e18e37ecf92d52c78068c881b594d4691db74bcb2c76a

Tx prefix hash: 6624049e6ad4f184b99345f10d4a67dda18cfc5770619b08cd4b387201070fe7
Tx public key: 2b59f1e0afba4e3d0ad50d62f96526acc95e7155272bb9a8dbb1adb8889ee292
Timestamp: 1708252490 Timestamp [UCT]: 2024-02-18 10:34:50 Age [y:d:h:m:s]: 01:037:09:25:23
Block: 960164 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287731 RingCT/type: yes/0
Extra: 012b59f1e0afba4e3d0ad50d62f96526acc95e7155272bb9a8dbb1adb8889ee2920211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8b0472aa7826570a209e6993a612751d746e4717a18f7d809479c9d6be342e08 0.600000000000 1419725 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": 960174, "vin": [ { "gen": { "height": 960164 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8b0472aa7826570a209e6993a612751d746e4717a18f7d809479c9d6be342e08" } } ], "extra": [ 1, 43, 89, 241, 224, 175, 186, 78, 61, 10, 213, 13, 98, 249, 101, 38, 172, 201, 94, 113, 85, 39, 43, 185, 168, 219, 177, 173, 184, 136, 158, 226, 146, 2, 17, 0, 0, 0, 9, 122, 156, 244, 199, 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