Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e87a9f8c6fb63f51fb24b29e9bca4eb44589e33c5626e96ce26c131988f15a20

Tx prefix hash: 17a66b004fe63e4746c8dedac531fdadb80e926ec7492db945e112981dc478dd
Tx public key: 855d5f89b2811a21f6f82c95256e5ed3c44641cdeb19af8a323f6f4a7d98b1f5
Timestamp: 1583010020 Timestamp [UCT]: 2020-02-29 21:00:20 Age [y:d:h:m:s]: 05:223:14:17:00
Block: 74377 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1311744 RingCT/type: yes/0
Extra: 01855d5f89b2811a21f6f82c95256e5ed3c44641cdeb19af8a323f6f4a7d98b1f50211000001570aca7173000000000000000000

1 output(s) for total of 347.989726272000 dcy

stealth address amount amount idx
00: 906fee605a3a47f3f70dcaf1b3a5deef56f527a9d427747f98d2e7c74019eca2 347.989726272000 137608 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": 74387, "vin": [ { "gen": { "height": 74377 } } ], "vout": [ { "amount": 347989726272, "target": { "key": "906fee605a3a47f3f70dcaf1b3a5deef56f527a9d427747f98d2e7c74019eca2" } } ], "extra": [ 1, 133, 93, 95, 137, 178, 129, 26, 33, 246, 248, 44, 149, 37, 110, 94, 211, 196, 70, 65, 205, 235, 25, 175, 138, 50, 63, 111, 74, 125, 152, 177, 245, 2, 17, 0, 0, 1, 87, 10, 202, 113, 115, 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