Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4393d1efed377debbac79a96bf1b0d1634fd57933c58752d5d93b53e75319e7c

Tx prefix hash: b1948d8dc1e52835fab13515872fcc0f5a323730ff3d8dedd7a6434fa7dee7a9
Tx public key: bdada670df1823d238d2893d2161e194b0c87e8c36d4d93e1f282cc3fc2ce211
Timestamp: 1715365709 Timestamp [UCT]: 2024-05-10 18:28:29 Age [y:d:h:m:s]: 00:331:19:03:27
Block: 1019144 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237145 RingCT/type: yes/0
Extra: 01bdada670df1823d238d2893d2161e194b0c87e8c36d4d93e1f282cc3fc2ce211021100000001679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e504f24ad2744cd7f8304849b67f3badc92a93414420b929194cb6353300e897 0.600000000000 1483037 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": 1019154, "vin": [ { "gen": { "height": 1019144 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e504f24ad2744cd7f8304849b67f3badc92a93414420b929194cb6353300e897" } } ], "extra": [ 1, 189, 173, 166, 112, 223, 24, 35, 210, 56, 210, 137, 61, 33, 97, 225, 148, 176, 200, 126, 140, 54, 212, 217, 62, 31, 40, 44, 195, 252, 44, 226, 17, 2, 17, 0, 0, 0, 1, 103, 154, 138, 129, 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