Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be3334bcf9929a101498812b93d9e3f1381effcd276bd1e7d4e83da336cbec03

Tx prefix hash: 0c7be2072ac580fd593dfb913e04071ee9a9ff0fb39f30b5e2d7c8e048c902fe
Tx public key: a9a5e3eb7ada0e178fe9e8eabacc10a6e5a403f5582d7438ef8d684af5bf996f
Timestamp: 1616037372 Timestamp [UCT]: 2021-03-18 03:16:12 Age [y:d:h:m:s]: 03:308:20:00:13
Block: 220912 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 980111 RingCT/type: yes/0
Extra: 01a9a5e3eb7ada0e178fe9e8eabacc10a6e5a403f5582d7438ef8d684af5bf996f02110000006590ec05ad000000000000000000

1 output(s) for total of 113.769915085000 dcy

stealth address amount amount idx
00: f249ca99cd8677bc32bff975a0881f7fd6bdd485e5d0ba0fba3ccbc66509f148 113.769915085000 455156 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": 220922, "vin": [ { "gen": { "height": 220912 } } ], "vout": [ { "amount": 113769915085, "target": { "key": "f249ca99cd8677bc32bff975a0881f7fd6bdd485e5d0ba0fba3ccbc66509f148" } } ], "extra": [ 1, 169, 165, 227, 235, 122, 218, 14, 23, 143, 233, 232, 234, 186, 204, 16, 166, 229, 164, 3, 245, 88, 45, 116, 56, 239, 141, 104, 74, 245, 191, 153, 111, 2, 17, 0, 0, 0, 101, 144, 236, 5, 173, 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