Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2f596c8bdb84151e52ef0ffa64bf0c76485c8dce74f76123875c06a634df36c

Tx prefix hash: 332d7b3083b7647e27ed3dc5558478d9f35f6f5d5490c82c27d0a122a81b0330
Tx public key: 8017e265f6ea84966e97ee9815f5b4acbb498af80169757c4f42b83dfe3faf8d
Timestamp: 1783735667 Timestamp [UTC]: 2026-07-11 02:07:47 Age [y:d:h:m:s]: 00:131:13:06:54
Block: 1579552 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 102421 RingCT/type: yes/0
Extra: 018017e265f6ea84966e97ee9815f5b4acbb498af80169757c4f42b83dfe3faf8d02085e1a0fc7ecfe7fc9

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 6c9930a4c7339b8aedb2592fd4da3a1aba83d819405c917cc31e61258a5d856f 0.000600000000 2069544 of 15 <23>

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": 1579562, "vin": [ { "gen": { "height": 1579552 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "6c9930a4c7339b8aedb2592fd4da3a1aba83d819405c917cc31e61258a5d856f", "view_tag": "23" } } } ], "extra": [ 1, 128, 23, 226, 101, 246, 234, 132, 150, 110, 151, 238, 152, 21, 245, 180, 172, 187, 73, 138, 248, 1, 105, 117, 124, 79, 66, 184, 61, 254, 63, 175, 141, 2, 8, 94, 26, 15, 199, 236, 254, 127, 201 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: