Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6fa18437bade635dbe61eb9a454eab54e7efd8e8fcfbb20cf1e005867dc03dfa

Tx prefix hash: e50f74bbdfe08709cb3895fbd6fe5d7654b315c962f7ae4a9177f4d0c54cf44f
Tx public key: 0bf33ecfe53f8ebe6433ebacfde3365a0907a65a2a1883bad8a7a78352347858
Timestamp: 1774961520 Timestamp [UTC]: 2026-03-31 12:52:00 Age [y:d:h:m:s]: 00:194:19:00:33
Block: 1509805 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142870 RingCT/type: yes/0
Extra: 010bf33ecfe53f8ebe6433ebacfde3365a0907a65a2a1883bad8a7a78352347858021100000002e3d7dc9f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a8439468692b4b0cb9c85c8bf2d4723e56ebfe17700e5079ac47b324ba310cc4 0.000600000000 1999581 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": 1509815, "vin": [ { "gen": { "height": 1509805 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a8439468692b4b0cb9c85c8bf2d4723e56ebfe17700e5079ac47b324ba310cc4" } } ], "extra": [ 1, 11, 243, 62, 207, 229, 63, 142, 190, 100, 51, 235, 172, 253, 227, 54, 90, 9, 7, 166, 90, 42, 24, 131, 186, 216, 167, 167, 131, 82, 52, 120, 88, 2, 17, 0, 0, 0, 2, 227, 215, 220, 159, 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: