Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73a1abd5ced0b488094908270130f8ea195369b8d35cb5772633b967ef0596d7

Tx prefix hash: 9f3a993c6cfb697f4b461f2f1643fcc9c91d2cf853487d173a863c5417d8420c
Tx public key: 1ac1db7799f7eb747353f4c0cf5d46b73f3674be0b3d22eb619453c66bad868e
Timestamp: 1686035733 Timestamp [UCT]: 2023-06-06 07:15:33 Age [y:d:h:m:s]: 01:224:11:17:19
Block: 776222 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 421835 RingCT/type: yes/0
Extra: 011ac1db7799f7eb747353f4c0cf5d46b73f3674be0b3d22eb619453c66bad868e02110000000275e3f0e9000000000000000000

1 output(s) for total of 1.644577914000 dcy

stealth address amount amount idx
00: 16479aff4e92e44e3b77f975134add7c4e31d343cb35b88994d4feb088e4d5d6 1.644577914000 1225759 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": 776232, "vin": [ { "gen": { "height": 776222 } } ], "vout": [ { "amount": 1644577914, "target": { "key": "16479aff4e92e44e3b77f975134add7c4e31d343cb35b88994d4feb088e4d5d6" } } ], "extra": [ 1, 26, 193, 219, 119, 153, 247, 235, 116, 115, 83, 244, 192, 207, 93, 70, 183, 63, 54, 116, 190, 11, 61, 34, 235, 97, 148, 83, 198, 107, 173, 134, 142, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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