Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5010b2cf136d40d8c98c466ecb4b9517c0c6409e3f1d5cf76cd9aa81538c2a02

Tx prefix hash: ff970eb7897bfe8babbc2bfd89a8989458e223c7c2dbfb38bbc331927abe3a52
Tx public key: 5985ad3b940314630eb507e6e96c7ddd3a916b5b5b0f17ef697dd18af1a15be3
Timestamp: 1720944618 Timestamp [UCT]: 2024-07-14 08:10:18 Age [y:d:h:m:s]: 00:197:17:41:52
Block: 1065398 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 141223 RingCT/type: yes/0
Extra: 015985ad3b940314630eb507e6e96c7ddd3a916b5b5b0f17ef697dd18af1a15be302110000001091e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7f3ced3cee1b6611fb1d330741713605956ed6ff8b41a449353bbb93b39e493f 0.600000000000 1535943 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": 1065408, "vin": [ { "gen": { "height": 1065398 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f3ced3cee1b6611fb1d330741713605956ed6ff8b41a449353bbb93b39e493f" } } ], "extra": [ 1, 89, 133, 173, 59, 148, 3, 20, 99, 14, 181, 7, 230, 233, 108, 125, 221, 58, 145, 107, 91, 91, 15, 23, 239, 105, 125, 209, 138, 241, 161, 91, 227, 2, 17, 0, 0, 0, 16, 145, 225, 60, 4, 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