Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d7242c5909f2d0cb4f4502a5bae8e32fa0666841c30aed793e813a0c47c91dc

Tx prefix hash: 124cafa8b48eba9ffe64d74dca3591fcaf783d1cd46da2fe2681ce058fff7f41
Tx public key: 7ad9f7d9b624fe8fd607aa123878dd7a7f30b043d9bf89657e363f6c57ebed3e
Timestamp: 1733546051 Timestamp [UCT]: 2024-12-07 04:34:11 Age [y:d:h:m:s]: 00:140:01:27:10
Block: 1169753 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99915 RingCT/type: yes/0
Extra: 017ad9f7d9b624fe8fd607aa123878dd7a7f30b043d9bf89657e363f6c57ebed3e021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 506db3dab09b005dfc5a56045df67e667622d88971ca1515fbccf2c69ebf7844 0.600000000000 1655476 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": 1169763, "vin": [ { "gen": { "height": 1169753 } } ], "vout": [ { "amount": 600000000, "target": { "key": "506db3dab09b005dfc5a56045df67e667622d88971ca1515fbccf2c69ebf7844" } } ], "extra": [ 1, 122, 217, 247, 217, 182, 36, 254, 143, 214, 7, 170, 18, 56, 120, 221, 122, 127, 48, 176, 67, 217, 191, 137, 101, 126, 54, 63, 108, 87, 235, 237, 62, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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