Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d466479f79727b66400c3f4874b4180aa2646abdf1262a0cf562badeffd04371

Tx prefix hash: 3f7d988881fcb3eaad28b81ad624d6e77f2a72a85d0d5a2bfa70a13b0b10cda4
Tx public key: a20427479a17a7e81a3bccf7c1e9176b8ed43c575cdf4fe4f48fff8116e4f294
Timestamp: 1675278985 Timestamp [UCT]: 2023-02-01 19:16:25 Age [y:d:h:m:s]: 01:349:03:36:14
Block: 687675 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 510516 RingCT/type: yes/0
Extra: 01a20427479a17a7e81a3bccf7c1e9176b8ed43c575cdf4fe4f48fff8116e4f294021100000003e6d27f9c000000000000000000

1 output(s) for total of 3.231820183000 dcy

stealth address amount amount idx
00: f1771829d29958bb71b49fe77e2a54d3d2211c4b381b08b9760b5f4d43721f5d 3.231820183000 1130256 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": 687685, "vin": [ { "gen": { "height": 687675 } } ], "vout": [ { "amount": 3231820183, "target": { "key": "f1771829d29958bb71b49fe77e2a54d3d2211c4b381b08b9760b5f4d43721f5d" } } ], "extra": [ 1, 162, 4, 39, 71, 154, 23, 167, 232, 26, 59, 204, 247, 193, 233, 23, 107, 142, 212, 60, 87, 92, 223, 79, 228, 244, 143, 255, 129, 22, 228, 242, 148, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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