Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f039638bd63bce60ab5c24f67829d47d043c03736b5b94e485e725085204043

Tx prefix hash: e1e557231e1cc3eabbee2431075b02037e54aa9c27105f275c5f53f2b575b85e
Tx public key: 8f9ae5e293b3ee2589c1045b1438b93b3580f49e8a62c925aa3d9101b9b6b182
Timestamp: 1583848896 Timestamp [UCT]: 2020-03-10 14:01:36 Age [y:d:h:m:s]: 04:350:15:09:53
Block: 79665 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1145610 RingCT/type: yes/0
Extra: 018f9ae5e293b3ee2589c1045b1438b93b3580f49e8a62c925aa3d9101b9b6b1820211000000013b1b9791000000000000000000

1 output(s) for total of 334.223955650000 dcy

stealth address amount amount idx
00: 10df3460a2370f0d4d1a0e17c55db7b986bfe0221699077a22af9e703d613440 334.223955650000 145813 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": 79675, "vin": [ { "gen": { "height": 79665 } } ], "vout": [ { "amount": 334223955650, "target": { "key": "10df3460a2370f0d4d1a0e17c55db7b986bfe0221699077a22af9e703d613440" } } ], "extra": [ 1, 143, 154, 229, 226, 147, 179, 238, 37, 137, 193, 4, 91, 20, 56, 185, 59, 53, 128, 244, 158, 138, 98, 201, 37, 170, 61, 145, 1, 185, 182, 177, 130, 2, 17, 0, 0, 0, 1, 59, 27, 151, 145, 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