Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fce19c39cb3fc5905e87f0a92d6be278af35dc0dff6e254aaca309b58db4f2d4

Tx prefix hash: 443e321160d51c55b937b71bd389df8828319beeeb6bafef9c70d03611e9539d
Tx public key: d99674b7462ba6c24ecd889025ad04256413d719ae5262c237d9e8e0ce69ec81
Timestamp: 1583869706 Timestamp [UTC]: 2020-03-10 19:48:26 Age [y:d:h:m:s]: 06:252:12:27:32
Block: 80102 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1600151 RingCT/type: yes/0
Extra: 01d99674b7462ba6c24ecd889025ad04256413d719ae5262c237d9e8e0ce69ec81021100000014a08fd034000000000000000000

1 output(s) for total of 0.333111489099 xmr

stealth address amount amount idx tag
00: 4ef0ba93baa4576ea9ac52624220b15f5ab521aa9bd98955fa1ec4b7b9c46698 0.333111489099 146592 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 dinastycoin-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": 80112, "vin": [ { "gen": { "height": 80102 } } ], "vout": [ { "amount": 333111489099, "target": { "key": "4ef0ba93baa4576ea9ac52624220b15f5ab521aa9bd98955fa1ec4b7b9c46698" } } ], "extra": [ 1, 217, 150, 116, 183, 70, 43, 166, 194, 78, 205, 136, 144, 37, 173, 4, 37, 100, 19, 215, 25, 174, 82, 98, 194, 55, 217, 232, 224, 206, 105, 236, 129, 2, 17, 0, 0, 0, 20, 160, 143, 208, 52, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: