Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd7d99c7423295878e8270018a82ca4dd8c0d71f1f7b145302cbfec5ddcbca58

Tx prefix hash: 0bebe4c501e63103e1e7c082c080f8b44ac1bdcf19aae10a3ed5a20b26860817
Tx public key: 16a740d4c92a434214cc2fca909e1728ba409f5f6cf9dbb3e206ccd216e4c325
Timestamp: 1583347856 Timestamp [UCT]: 2020-03-04 18:50:56 Age [y:d:h:m:s]: 04:297:01:23:39
Block: 76540 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1106563 RingCT/type: yes/0
Extra: 0116a740d4c92a434214cc2fca909e1728ba409f5f6cf9dbb3e206ccd216e4c32502110000002b0aca7173000000000000000000

1 output(s) for total of 342.288258455000 dcy

stealth address amount amount idx
00: 0f3f961970f4d32dbfafda8487c6d6bc861b45a55fb3aca9bf1137036e002459 342.288258455000 140816 of 0

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": 76550, "vin": [ { "gen": { "height": 76540 } } ], "vout": [ { "amount": 342288258455, "target": { "key": "0f3f961970f4d32dbfafda8487c6d6bc861b45a55fb3aca9bf1137036e002459" } } ], "extra": [ 1, 22, 167, 64, 212, 201, 42, 67, 66, 20, 204, 47, 202, 144, 158, 23, 40, 186, 64, 159, 95, 108, 249, 219, 179, 226, 6, 204, 210, 22, 228, 195, 37, 2, 17, 0, 0, 0, 43, 10, 202, 113, 115, 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