Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ee3d9a1b28f9a99583adbd94907353b16f3622a5b72d1e9fd2fd56cd033c4a7

Tx prefix hash: 4f7fb02bc75105f2c9b3d957809b50abd6a07df0d28f5b38ae5fd3944721c2cf
Tx public key: b1dbe614ea96d3f5e5af8b1587fd4da73ec07441a502695c25ef92c74598502e
Timestamp: 1720698903 Timestamp [UTC]: 2024-07-11 11:55:03 Age [y:d:h:m:s]: 01:311:14:53:12
Block: 1063357 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 474176 RingCT/type: yes/0
Extra: 01b1dbe614ea96d3f5e5af8b1587fd4da73ec07441a502695c25ef92c74598502e02110000000591e13c04000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 57e321aa420ae43aec71a6d7110e44b5542ffed31fe0e2e1620552148c3f4f98 0.000600000000 1533872 of 15 -

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": 1063367, "vin": [ { "gen": { "height": 1063357 } } ], "vout": [ { "amount": 600000000, "target": { "key": "57e321aa420ae43aec71a6d7110e44b5542ffed31fe0e2e1620552148c3f4f98" } } ], "extra": [ 1, 177, 219, 230, 20, 234, 150, 211, 245, 229, 175, 139, 21, 135, 253, 77, 167, 62, 192, 116, 65, 165, 2, 105, 92, 37, 239, 146, 199, 69, 152, 80, 46, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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: