Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3ee7c02bf54c4b31c48de3c92690fc68673d4aa5d4cb51b182f9984521436bd

Tx prefix hash: 073f6197ca510c7dd84df2bdad118fd7f6089325508fab1be14647cbc082d9f1
Tx public key: e634fd3fc2bff8d2a9d4ffc31b6f7963b037a8d0ed7121de943e75b27ae4bd27
Timestamp: 1577811811 Timestamp [UCT]: 2019-12-31 17:03:31 Age [y:d:h:m:s]: 04:363:15:52:34
Block: 35901 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1149006 RingCT/type: yes/0
Extra: 01e634fd3fc2bff8d2a9d4ffc31b6f7963b037a8d0ed7121de943e75b27ae4bd2702110000006d8a2ee0d9000000000000000000

1 output(s) for total of 466.708743742000 dcy

stealth address amount amount idx
00: 5626a471e7a30d3cf90392d35ca0dfc19ad97b958dee8d37fac0207ce6d0d095 466.708743742000 60628 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": 35911, "vin": [ { "gen": { "height": 35901 } } ], "vout": [ { "amount": 466708743742, "target": { "key": "5626a471e7a30d3cf90392d35ca0dfc19ad97b958dee8d37fac0207ce6d0d095" } } ], "extra": [ 1, 230, 52, 253, 63, 194, 191, 248, 210, 169, 212, 255, 195, 27, 111, 121, 99, 176, 55, 168, 208, 237, 113, 33, 222, 148, 62, 117, 178, 122, 228, 189, 39, 2, 17, 0, 0, 0, 109, 138, 46, 224, 217, 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