Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bda71d343edb95e2fb430da7c1c8c4a6186dba72da72d8e492cbfa30c60d4ff2

Tx prefix hash: eb1cb50762975038ac6ba5fb0f57f60b5577e5fb94cdfe6c5cd63f11abb8ea0e
Tx public key: 979fc8392abda1092d4b3f1f36d9f7de7f7ad3e23dc5d53e379be906691a4c34
Timestamp: 1789185261 Timestamp [UTC]: 2026-09-12 03:54:21 Age [y:d:h:m:s]: 00:067:06:15:24
Block: 1633549 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 47507 RingCT/type: yes/0
Extra: 01979fc8392abda1092d4b3f1f36d9f7de7f7ad3e23dc5d53e379be906691a4c34

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: f6b0a9f75303371f66b21b58c58a4404b73facfe77f5c623b932591749f7b629 0.000600000000 2123579 of 15 <30>

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": 1633559, "vin": [ { "gen": { "height": 1633549 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "f6b0a9f75303371f66b21b58c58a4404b73facfe77f5c623b932591749f7b629", "view_tag": "30" } } } ], "extra": [ 1, 151, 159, 200, 57, 42, 189, 161, 9, 45, 75, 63, 31, 54, 217, 247, 222, 127, 122, 211, 226, 61, 197, 213, 62, 55, 155, 233, 6, 105, 26, 76, 52 ], "rct_signatures": { "type": 0 } }


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