Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e985acdf029de7e6666726484fafaa439ec862a3adbdd280b3b17eb5a4b48d65

Tx prefix hash: 6d1eec680e29a8ea23274782932c55c9f28960e297d5194407077504b68d62c2
Tx public key: 0b7737dc0447f74ea0ea9b4befeabbf1af2684f7a83ba76d27b5ab357f22bad0
Timestamp: 1731745676 Timestamp [UCT]: 2024-11-16 08:27:56 Age [y:d:h:m:s]: 00:203:20:14:04
Block: 1154843 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145550 RingCT/type: yes/0
Extra: 010b7737dc0447f74ea0ea9b4befeabbf1af2684f7a83ba76d27b5ab357f22bad0021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f7d12bae2631bcc2faca811a88b7efe4551e56f9f8d41d0a2fb9add88746af2a 0.600000000000 1640456 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": 1154853, "vin": [ { "gen": { "height": 1154843 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f7d12bae2631bcc2faca811a88b7efe4551e56f9f8d41d0a2fb9add88746af2a" } } ], "extra": [ 1, 11, 119, 55, 220, 4, 71, 247, 78, 160, 234, 155, 75, 239, 234, 187, 241, 175, 38, 132, 247, 168, 59, 167, 109, 39, 181, 171, 53, 127, 34, 186, 208, 2, 17, 0, 0, 0, 6, 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