Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ad5a142db85b57e3e49fc8054f7dcd628c23c0dd7355bbe03080ab300516d5d

Tx prefix hash: 6705610f73bf76be00c7bea7268da4441ea6c429624d68e4491f48517fc67b73
Tx public key: 68cc3b3cd2d78292c030812694d21ea436aa1d1453d5a7d657ff371d39d8fe42
Timestamp: 1732540057 Timestamp [UCT]: 2024-11-25 13:07:37 Age [y:d:h:m:s]: 00:141:10:52:49
Block: 1161425 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100907 RingCT/type: yes/0
Extra: 0168cc3b3cd2d78292c030812694d21ea436aa1d1453d5a7d657ff371d39d8fe42021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1fc9ccd931d03bb7b8f8de0ae91e21f3cb79928afa865d0939dbdc526f9c3059 0.600000000000 1647080 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": 1161435, "vin": [ { "gen": { "height": 1161425 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1fc9ccd931d03bb7b8f8de0ae91e21f3cb79928afa865d0939dbdc526f9c3059" } } ], "extra": [ 1, 104, 204, 59, 60, 210, 215, 130, 146, 192, 48, 129, 38, 148, 210, 30, 164, 54, 170, 29, 20, 83, 213, 167, 214, 87, 255, 55, 29, 57, 216, 254, 66, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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