Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5169388898ea9380df3662028900c0282b1cd5f70af09e16dc5925da004782c8

Tx prefix hash: 47122baac2849cde694503bc77e7f96a116b2bd00a7c283d9a05bacf5964595b
Tx public key: 25f827116a9758af2655b2494c6bf8cc6af29d6b4069eed2cc3062b8138ba08e
Timestamp: 1574616283 Timestamp [UTC]: 2019-11-24 17:24:43 Age [y:d:h:m:s]: 06:301:15:07:59
Block: 16587 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1622916 RingCT/type: yes/0
Extra: 0125f827116a9758af2655b2494c6bf8cc6af29d6b4069eed2cc3062b8138ba08e021100000002f95225a5000000000000000000

1 output(s) for total of 0.540805706091 xmr

stealth address amount amount idx tag
00: 1511e2eb99f277d06bd882aa990d22c300dcc0b83b55290e148e5078e9d515c6 0.540805706091 23284 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": 16597, "vin": [ { "gen": { "height": 16587 } } ], "vout": [ { "amount": 540805706091, "target": { "key": "1511e2eb99f277d06bd882aa990d22c300dcc0b83b55290e148e5078e9d515c6" } } ], "extra": [ 1, 37, 248, 39, 17, 106, 151, 88, 175, 38, 85, 178, 73, 76, 107, 248, 204, 106, 242, 157, 107, 64, 105, 238, 210, 204, 48, 98, 184, 19, 139, 160, 142, 2, 17, 0, 0, 0, 2, 249, 82, 37, 165, 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: