Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a577ea31c0d7759957bb7d396ca4f696708f8078293ee44f11d4af5aa13f9d42

Tx prefix hash: 04adeea66bc23ab05e7c07e934ff62515d93842b1a84bd0451dd25b0ce821f7c
Tx public key: 6614aef89f50332747afbf16f12cf6d2b1c77c52f4a396a7c3c693eaeec51eef
Timestamp: 1709014441 Timestamp [UCT]: 2024-02-27 06:14:01 Age [y:d:h:m:s]: 01:050:13:07:00
Block: 966491 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297125 RingCT/type: yes/0
Extra: 016614aef89f50332747afbf16f12cf6d2b1c77c52f4a396a7c3c693eaeec51eef02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3c5bb0b14297edeb9484540f7e38dd0ac5bf74c74ba27817b4efc45974884b86 0.600000000000 1426248 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": 966501, "vin": [ { "gen": { "height": 966491 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3c5bb0b14297edeb9484540f7e38dd0ac5bf74c74ba27817b4efc45974884b86" } } ], "extra": [ 1, 102, 20, 174, 248, 159, 80, 51, 39, 71, 175, 191, 22, 241, 44, 246, 210, 177, 199, 124, 82, 244, 163, 150, 167, 195, 198, 147, 234, 238, 197, 30, 239, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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