Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9b55ee637a84814b2b5fe31d6277ea0955351e0353a569bc2ab00838b9cfed7

Tx prefix hash: 687ec0a4580ce2b34c3c5e979fbc801c59b86f4b9fcccfdb9ae5b209be2a62a0
Tx public key: b30767fdaa7586f1092cd2a9e4efa188eb31593930b8931160045c9215af8c77
Timestamp: 1634499062 Timestamp [UCT]: 2021-10-17 19:31:02 Age [y:d:h:m:s]: 03:074:23:57:44
Block: 355109 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 831535 RingCT/type: yes/0
Extra: 01b30767fdaa7586f1092cd2a9e4efa188eb31593930b8931160045c9215af8c770211000000085d7cc334000000000000000000

1 output(s) for total of 40.867388496000 dcy

stealth address amount amount idx
00: d3abff44f8391eaf0e3099eb785452329c0c0c75a991dfa2935e7267a7f891c6 40.867388496000 725113 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": 355119, "vin": [ { "gen": { "height": 355109 } } ], "vout": [ { "amount": 40867388496, "target": { "key": "d3abff44f8391eaf0e3099eb785452329c0c0c75a991dfa2935e7267a7f891c6" } } ], "extra": [ 1, 179, 7, 103, 253, 170, 117, 134, 241, 9, 44, 210, 169, 228, 239, 161, 136, 235, 49, 89, 57, 48, 184, 147, 17, 96, 4, 92, 146, 21, 175, 140, 119, 2, 17, 0, 0, 0, 8, 93, 124, 195, 52, 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