Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0bd198372181aa94e10a39e0fbbbf04ea7d6e73d5b5748aba1d6ab4b32501076

Tx prefix hash: 7f17dbe602fb31280d2788b389de5252edde0c6c16c91cbdd76ee225b2a868e6
Tx public key: 8bc00f1b53455203320507f8b3bf40955dae8efdfde944eb0abb10352529e252
Timestamp: 1743356926 Timestamp [UTC]: 2025-03-30 17:48:46 Age [y:d:h:m:s]: 00:323:20:21:03
Block: 1250705 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229109 RingCT/type: yes/0
Extra: 018bc00f1b53455203320507f8b3bf40955dae8efdfde944eb0abb10352529e2520211000000021a970403000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a22aea89ff3d885c0ff087d53305d001ef6a8f2697076adce7d8ad4cfe3d3b44 0.000600000000 1737756 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": 1250715, "vin": [ { "gen": { "height": 1250705 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a22aea89ff3d885c0ff087d53305d001ef6a8f2697076adce7d8ad4cfe3d3b44" } } ], "extra": [ 1, 139, 192, 15, 27, 83, 69, 82, 3, 50, 5, 7, 248, 179, 191, 64, 149, 93, 174, 142, 253, 253, 233, 68, 235, 10, 187, 16, 53, 37, 41, 226, 82, 2, 17, 0, 0, 0, 2, 26, 151, 4, 3, 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) | dinastycoin version: tesla-369