Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0607d4c8ce4c9bb4ccde8f76347b19a70144a7ca1a16172edd97aa4845a0df21

Tx prefix hash: 4ec89620fd8c53154709f2c71202ebbf191bd4aee66d9fefc8c845750e2b5cfb
Tx public key: 652cb00a178283f3cbdddb805de48ae7498287dc950424dccc649d17309a6bcd
Timestamp: 1701073285 Timestamp [UCT]: 2023-11-27 08:21:25 Age [y:d:h:m:s]: 01:131:18:37:45
Block: 900641 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 355327 RingCT/type: yes/0
Extra: 01652cb00a178283f3cbdddb805de48ae7498287dc950424dccc649d17309a6bcd02110000000133af99f4000000000000000000

1 output(s) for total of 0.636505961000 dcy

stealth address amount amount idx
00: beff7500831fe67af47c188cde7e0ca0f3b9f0a77500c2c314b80ff033f0e6e0 0.636505961000 1357152 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": 900651, "vin": [ { "gen": { "height": 900641 } } ], "vout": [ { "amount": 636505961, "target": { "key": "beff7500831fe67af47c188cde7e0ca0f3b9f0a77500c2c314b80ff033f0e6e0" } } ], "extra": [ 1, 101, 44, 176, 10, 23, 130, 131, 243, 203, 221, 219, 128, 93, 228, 138, 231, 73, 130, 135, 220, 149, 4, 36, 220, 204, 100, 157, 23, 48, 154, 107, 205, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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