Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6092783aeeb90e73a7eb9c48dace5d557af97492d2da1229ace6ab18136dcf5c

Tx prefix hash: d6658f2f05471574c03622b9d196b1fb94b461eeef07b703a23042dfbc38ede3
Tx public key: 9010b4386b7d05f3729c411a1286461d5dd19d0161890f42d163c993fe1585e2
Timestamp: 1673128160 Timestamp [UTC]: 2023-01-07 21:49:20 Age [y:d:h:m:s]: 03:132:01:17:55
Block: 669832 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 867286 RingCT/type: yes/0
Extra: 019010b4386b7d05f3729c411a1286461d5dd19d0161890f42d163c993fe1585e202110000000283600029000000000000000000

1 output(s) for total of 0.003703125929 xmr

stealth address amount amount idx tag
00: a3ebe38fd695cf803952c26e3420c93f0a7042e92fd4959f403ef068af2447b4 0.003703125929 1111195 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": 669842, "vin": [ { "gen": { "height": 669832 } } ], "vout": [ { "amount": 3703125929, "target": { "key": "a3ebe38fd695cf803952c26e3420c93f0a7042e92fd4959f403ef068af2447b4" } } ], "extra": [ 1, 144, 16, 180, 56, 107, 125, 5, 243, 114, 156, 65, 26, 18, 134, 70, 29, 93, 209, 157, 1, 97, 137, 15, 66, 209, 99, 201, 147, 254, 21, 133, 226, 2, 17, 0, 0, 0, 2, 131, 96, 0, 41, 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: