Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a826d2aedd6de7425262f203b89296b8bdd6f0aa4e2b0fc915f4ad1c7a7c198

Tx prefix hash: fa600d3993d7ef0a6b37908174fd3f7971f2c7f5aa80b7cab62eb58bdb5ec8d6
Tx public key: b645bb155e0c87f3b2aea3d417b8abd11984d41d9986bb66653a912a1dafb44e
Timestamp: 1577774320 Timestamp [UCT]: 2019-12-31 06:38:40 Age [y:d:h:m:s]: 04:325:18:19:51
Block: 35518 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1121968 RingCT/type: yes/0
Extra: 01b645bb155e0c87f3b2aea3d417b8abd11984d41d9986bb66653a912a1dafb44e0211000000084ac5aa02000000000000000000

1 output(s) for total of 468.122203447000 dcy

stealth address amount amount idx
00: 4674af5bcf65c3d6316cb592fa36c9278580285bc6b87eef4bcde54d34669962 468.122203447000 59934 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": 35528, "vin": [ { "gen": { "height": 35518 } } ], "vout": [ { "amount": 468122203447, "target": { "key": "4674af5bcf65c3d6316cb592fa36c9278580285bc6b87eef4bcde54d34669962" } } ], "extra": [ 1, 182, 69, 187, 21, 94, 12, 135, 243, 178, 174, 163, 212, 23, 184, 171, 209, 25, 132, 212, 29, 153, 134, 187, 102, 101, 58, 145, 42, 29, 175, 180, 78, 2, 17, 0, 0, 0, 8, 74, 197, 170, 2, 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