Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 467e18e6c90982c5ad542e6fda2809652e3c62d9c5657020a56d5522223312d4

Tx prefix hash: 07904c614b79523f584847cdd1559f2e2abec65e9eb2650b7e552c777be90b65
Tx public key: c5e4657e9a1e6053a62c068f39f8280210c78ee16cd9fc6a52c0e6838189d2df
Timestamp: 1633092380 Timestamp [UCT]: 2021-10-01 12:46:20 Age [y:d:h:m:s]: 03:143:00:03:31
Block: 344476 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 878885 RingCT/type: yes/0
Extra: 01c5e4657e9a1e6053a62c068f39f8280210c78ee16cd9fc6a52c0e6838189d2df0211000000065410958b000000000000000000

1 output(s) for total of 44.321656793000 dcy

stealth address amount amount idx
00: 7b8144c59d72c405995761bcaf7db83ba948293db6761bfa93016d3b25513b66 44.321656793000 706816 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": 344486, "vin": [ { "gen": { "height": 344476 } } ], "vout": [ { "amount": 44321656793, "target": { "key": "7b8144c59d72c405995761bcaf7db83ba948293db6761bfa93016d3b25513b66" } } ], "extra": [ 1, 197, 228, 101, 126, 154, 30, 96, 83, 166, 44, 6, 143, 57, 248, 40, 2, 16, 199, 142, 225, 108, 217, 252, 106, 82, 192, 230, 131, 129, 137, 210, 223, 2, 17, 0, 0, 0, 6, 84, 16, 149, 139, 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