Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f4fc599c244acb6be16f97ff6c1b623f766397bec4e39016ca1b5fa8d0c619f

Tx prefix hash: 5109c92a95166103a0f6c26c6aab20c5358f9e1baa8d471f6da0ccbda02892e2
Tx public key: c4a916b1657b9a233f35cb45d99030d0f69f2ce6538d0335618e109ebca29719
Timestamp: 1716100967 Timestamp [UTC]: 2024-05-19 06:42:47 Age [y:d:h:m:s]: 02:186:10:13:19
Block: 1025240 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 658254 RingCT/type: yes/0
Extra: 01c4a916b1657b9a233f35cb45d99030d0f69f2ce6538d0335618e109ebca297190211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 895c466555f976c882cfcaf02c3b2c0e5fc6d4a8b2aea21c2f6e3e5a31e91813 0.000600000000 1491597 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": 1025250, "vin": [ { "gen": { "height": 1025240 } } ], "vout": [ { "amount": 600000000, "target": { "key": "895c466555f976c882cfcaf02c3b2c0e5fc6d4a8b2aea21c2f6e3e5a31e91813" } } ], "extra": [ 1, 196, 169, 22, 177, 101, 123, 154, 35, 63, 53, 203, 69, 217, 144, 48, 208, 246, 159, 44, 230, 83, 141, 3, 53, 97, 142, 16, 158, 188, 162, 151, 25, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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: