Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5351d826ded7e771e3fef9fe6a8aae976d5280269c66435b970aa4e758707a49

Tx prefix hash: b16f6081c5ed945d8ac32adf840ef101dace34e4947cd0473c8937a0f0c6e70a
Tx public key: 59462be9386706e3cb85c123c11f6aab71c655af281db5864ea26f255d5ce14c
Timestamp: 1732738540 Timestamp [UCT]: 2024-11-27 20:15:40 Age [y:d:h:m:s]: 00:204:19:36:25
Block: 1163058 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 146089 RingCT/type: yes/0
Extra: 0159462be9386706e3cb85c123c11f6aab71c655af281db5864ea26f255d5ce14c021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d1243c42d827a91a9b85a5078a5c6c8e5234c0909e3fab08910bc8ef1d647ee 0.600000000000 1648723 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": 1163068, "vin": [ { "gen": { "height": 1163058 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d1243c42d827a91a9b85a5078a5c6c8e5234c0909e3fab08910bc8ef1d647ee" } } ], "extra": [ 1, 89, 70, 43, 233, 56, 103, 6, 227, 203, 133, 193, 35, 193, 31, 106, 171, 113, 198, 85, 175, 40, 29, 181, 134, 78, 162, 111, 37, 93, 92, 225, 76, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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