Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 76432ad7c38fce438e2c356676d0d5db809d58dce0ab1f09af30a748fe79710d

Tx prefix hash: 0312de591db93897ea6daa30c58e47ac1884a759a3f2f9805f847154f667ae8e
Tx public key: 2aa75a04bfa10dd452ce393429e8bbbab8fcf224fb2da583cc775d24eca5a484
Timestamp: 1587537559 Timestamp [UCT]: 2020-04-22 06:39:19 Age [y:d:h:m:s]: 04:292:19:39:25
Block: 95100 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1119387 RingCT/type: yes/0
Extra: 012aa75a04bfa10dd452ce393429e8bbbab8fcf224fb2da583cc775d24eca5a48402110000037aa86a1a65000000000000000000

1 output(s) for total of 297.094758743000 dcy

stealth address amount amount idx
00: 2dd88019e95fa99ad8aac9d5c4c0ba58170db3691800b7e4016e696ab5b0449f 297.094758743000 169016 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": 95110, "vin": [ { "gen": { "height": 95100 } } ], "vout": [ { "amount": 297094758743, "target": { "key": "2dd88019e95fa99ad8aac9d5c4c0ba58170db3691800b7e4016e696ab5b0449f" } } ], "extra": [ 1, 42, 167, 90, 4, 191, 161, 13, 212, 82, 206, 57, 52, 41, 232, 187, 186, 184, 252, 242, 36, 251, 45, 165, 131, 204, 119, 93, 36, 236, 165, 164, 132, 2, 17, 0, 0, 3, 122, 168, 106, 26, 101, 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