Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5fbf9e6d65c8a35850646d61d3e74682e3005e0bb3a45dbddebc672396765062

Tx prefix hash: 40801c1d0a70d72b88b5156976303495b8f92e92f7ddf6935145506db9e16ecf
Tx public key: 2920e9a076605b9b590b82e1b8a52530bb903124e178d8a847f12cb63f9e6b55
Timestamp: 1716552227 Timestamp [UCT]: 2024-05-24 12:03:47 Age [y:d:h:m:s]: 00:314:18:44:12
Block: 1028987 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 224969 RingCT/type: yes/0
Extra: 012920e9a076605b9b590b82e1b8a52530bb903124e178d8a847f12cb63f9e6b550211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 37676e54d854c2a7db22154141555874a3cb30401b6b38c0f60237d9f74b6d53 0.600000000000 1496988 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": 1028997, "vin": [ { "gen": { "height": 1028987 } } ], "vout": [ { "amount": 600000000, "target": { "key": "37676e54d854c2a7db22154141555874a3cb30401b6b38c0f60237d9f74b6d53" } } ], "extra": [ 1, 41, 32, 233, 160, 118, 96, 91, 155, 89, 11, 130, 225, 184, 165, 37, 48, 187, 144, 49, 36, 225, 120, 216, 168, 71, 241, 44, 182, 63, 158, 107, 85, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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