Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39540bba43446a90810d18f70dbb9828d00a23cd13b395fc6167702a5e271e7b

Tx prefix hash: 25de86c68e1933d8c49bf655ba3e1e05a20f94bf982043e566f96e31ba7b6267
Tx public key: a3d2d9c4b7ff5e82feac54d40ba34d706e17a2dbb1b1bda96b6d532453939781
Timestamp: 1724555660 Timestamp [UCT]: 2024-08-25 03:14:20 Age [y:d:h:m:s]: 00:224:14:00:59
Block: 1095349 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160335 RingCT/type: yes/0
Extra: 01a3d2d9c4b7ff5e82feac54d40ba34d706e17a2dbb1b1bda96b6d532453939781021100000001e337358e000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c9ccf13bc66d67a4803089b4fd1fc6bf3d540106af071b447a7914297d880ac5 0.600000000000 1570514 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": 1095359, "vin": [ { "gen": { "height": 1095349 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c9ccf13bc66d67a4803089b4fd1fc6bf3d540106af071b447a7914297d880ac5" } } ], "extra": [ 1, 163, 210, 217, 196, 183, 255, 94, 130, 254, 172, 84, 212, 11, 163, 77, 112, 110, 23, 162, 219, 177, 177, 189, 169, 107, 109, 83, 36, 83, 147, 151, 129, 2, 17, 0, 0, 0, 1, 227, 55, 53, 142, 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