Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7072f23364ecc98bd5ac8ee5a3c7e24a3c914d3e226d6e5251bf2d00cf72a577

Tx prefix hash: 8bdc09dac3637d7670cdfb214bb8f22af997c89e847e1d676ae57dd8ea30dc9a
Tx public key: cf6e936c79188cd2a206e614bc4959ec4e3f10412ef6e7abd2aef4cbe6ee0bbc
Timestamp: 1708878969 Timestamp [UTC]: 2024-02-25 16:36:09 Age [y:d:h:m:s]: 02:264:23:59:14
Block: 965366 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 714405 RingCT/type: yes/0
Extra: 01cf6e936c79188cd2a206e614bc4959ec4e3f10412ef6e7abd2aef4cbe6ee0bbc0211000000137a9cf4c7000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 0aa463e8a9d85ec29eb47d44db314217f11792fe172e1e1a1a941db17282a42d 0.000600000000 1425117 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": 965376, "vin": [ { "gen": { "height": 965366 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0aa463e8a9d85ec29eb47d44db314217f11792fe172e1e1a1a941db17282a42d" } } ], "extra": [ 1, 207, 110, 147, 108, 121, 24, 140, 210, 162, 6, 230, 20, 188, 73, 89, 236, 78, 63, 16, 65, 46, 246, 231, 171, 210, 174, 244, 203, 230, 238, 11, 188, 2, 17, 0, 0, 0, 19, 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: