Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 02a7ccbb3e81b80295fbefda4f7a63a8733c74c59176d5253395f9d12bb9d0fd

Tx prefix hash: 27039531ae744828428b7000bd795d96b063170d97efe3005f730894c1ce2b6a
Tx public key: 11672dc08a761b8e49958253ae4f8636e74e50e1bd7e9ac21c3c21e8b2c1984a
Timestamp: 1627609483 Timestamp [UCT]: 2021-07-30 01:44:43 Age [y:d:h:m:s]: 03:290:05:41:36
Block: 303537 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 979771 RingCT/type: yes/0
Extra: 0111672dc08a761b8e49958253ae4f8636e74e50e1bd7e9ac21c3c21e8b2c1984a021100000011e084ab86000000000000000000

1 output(s) for total of 60.569836327000 dcy

stealth address amount amount idx
00: 5f9128a56572aa39306891dbfc89e4035549160287470f93f5583bf654826c44 60.569836327000 633520 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": 303547, "vin": [ { "gen": { "height": 303537 } } ], "vout": [ { "amount": 60569836327, "target": { "key": "5f9128a56572aa39306891dbfc89e4035549160287470f93f5583bf654826c44" } } ], "extra": [ 1, 17, 103, 45, 192, 138, 118, 27, 142, 73, 149, 130, 83, 174, 79, 134, 54, 231, 78, 80, 225, 189, 126, 154, 194, 28, 60, 33, 232, 178, 193, 152, 74, 2, 17, 0, 0, 0, 17, 224, 132, 171, 134, 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