Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8b2be1671c59f1cccfab26f4783bfe2b2ebcd2c3cb9789e25f07309ed231360

Tx prefix hash: 8604c81def96d7efaf035c059c9a31de1277044ece02fa0de914401a9e0c06e8
Tx public key: 8a3e19fd7e429958863e6e58a71a80c66614eb8e125776e26464595171331469
Timestamp: 1758230056 Timestamp [UTC]: 2025-09-18 21:14:16 Age [y:d:h:m:s]: 01:055:19:49:41
Block: 1371389 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306146 RingCT/type: yes/0
Extra: 018a3e19fd7e429958863e6e58a71a80c66614eb8e125776e26464595171331469021100000006b2f784c4000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 69fddb94adfb9066a6be5683a99c7ceb98f152078d842abd1e45b2a8c06bc4a2 0.000600000000 1859466 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": 1371399, "vin": [ { "gen": { "height": 1371389 } } ], "vout": [ { "amount": 600000000, "target": { "key": "69fddb94adfb9066a6be5683a99c7ceb98f152078d842abd1e45b2a8c06bc4a2" } } ], "extra": [ 1, 138, 62, 25, 253, 126, 66, 153, 88, 134, 62, 110, 88, 167, 26, 128, 198, 102, 20, 235, 142, 18, 87, 118, 226, 100, 100, 89, 81, 113, 51, 20, 105, 2, 17, 0, 0, 0, 6, 178, 247, 132, 196, 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: