Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6460ab7e1d72796fc1bdbc396be09a4a0e4d88d5ae4513f808965c119000af97

Tx prefix hash: ad203f6385830dc5b2e327a2f924a55bef2b20550a05975418a5d951acb306d0
Tx public key: 56adf4e45ada105af9a23f75ef9a588dfbfeecb9e54908208ea57854132e3ab4
Timestamp: 1673016995 Timestamp [UCT]: 2023-01-06 14:56:35 Age [y:d:h:m:s]: 02:119:17:30:50
Block: 668904 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 607273 RingCT/type: yes/0
Extra: 0156adf4e45ada105af9a23f75ef9a588dfbfeecb9e54908208ea57854132e3ab402110000000171bd5189000000000000000000

1 output(s) for total of 3.729437484000 dcy

stealth address amount amount idx
00: bd4cf303315cf194d91e707f773f87f2794eb9e77f8f3b28684b929b1e234ead 3.729437484000 1110181 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": 668914, "vin": [ { "gen": { "height": 668904 } } ], "vout": [ { "amount": 3729437484, "target": { "key": "bd4cf303315cf194d91e707f773f87f2794eb9e77f8f3b28684b929b1e234ead" } } ], "extra": [ 1, 86, 173, 244, 228, 90, 218, 16, 90, 249, 162, 63, 117, 239, 154, 88, 141, 251, 254, 236, 185, 229, 73, 8, 32, 142, 165, 120, 84, 19, 46, 58, 180, 2, 17, 0, 0, 0, 1, 113, 189, 81, 137, 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