Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80de37d13514ca824464d02bd0b2eeec69b41d586116da011f8f43f192f61f42

Tx prefix hash: 9d3c6983600325576535b03ca49fd0795d53824a5df9d7a43c9e3b1b9375623c
Tx public key: 720a3017d79d85ac2071826a711a8e9f638e73817d79386b32cd63f3c7f8e38d
Timestamp: 1713573657 Timestamp [UCT]: 2024-04-20 00:40:57 Age [y:d:h:m:s]: 00:218:18:47:02
Block: 1004257 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 156643 RingCT/type: yes/0
Extra: 01720a3017d79d85ac2071826a711a8e9f638e73817d79386b32cd63f3c7f8e38d0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d27e1ac6f8b30136d493ab63cee6d55adf85e635f8c7a61f025b64d7815c1e81 0.600000000000 1464825 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": 1004267, "vin": [ { "gen": { "height": 1004257 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d27e1ac6f8b30136d493ab63cee6d55adf85e635f8c7a61f025b64d7815c1e81" } } ], "extra": [ 1, 114, 10, 48, 23, 215, 157, 133, 172, 32, 113, 130, 106, 113, 26, 142, 159, 99, 142, 115, 129, 125, 121, 56, 107, 50, 205, 99, 243, 199, 248, 227, 141, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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