Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 20050c7d6c168c433f3638c1bce0c3dc65ea158d8e3c5620cfe83f13f78dcd99

Tx prefix hash: 35ae0f81352bf7d2b9f594ec1c73de3e380b7cfb1f21607d224b99e3e8f116d6
Tx public key: 444267f5a0697844563380e56fe54ecc17afa415854c48d44868b0494feaca22
Timestamp: 1759100501 Timestamp [UTC]: 2025-09-28 23:01:41 Age [y:d:h:m:s]: 00:232:14:04:34
Block: 1378598 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159677 RingCT/type: yes/0
Extra: 01444267f5a0697844563380e56fe54ecc17afa415854c48d44868b0494feaca22021100000002a5dccd79000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 8271bda85855db0ff66a5acf8be251d9cbad620f313d98cdc1b8cdec2daa860e 0.000600000000 1866693 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": 1378608, "vin": [ { "gen": { "height": 1378598 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8271bda85855db0ff66a5acf8be251d9cbad620f313d98cdc1b8cdec2daa860e" } } ], "extra": [ 1, 68, 66, 103, 245, 160, 105, 120, 68, 86, 51, 128, 229, 111, 229, 78, 204, 23, 175, 164, 21, 133, 76, 72, 212, 72, 104, 176, 73, 79, 234, 202, 34, 2, 17, 0, 0, 0, 2, 165, 220, 205, 121, 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: