Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 28fbc92ff6db892a007f8987b645b9af4e88b5201fedc1e9241ccbfd1d305270

Tx prefix hash: 369fdad8e64adf36f7f5035ce2e875bea1b3786c2f77e39d2b09f177d8121365
Tx public key: a1a07b94a269324d2b882ddb1b5ff03298525a7af9162d4f52deb203d1338ba5
Timestamp: 1774821294 Timestamp [UTC]: 2026-03-29 21:54:54 Age [y:d:h:m:s]: 00:233:23:51:16
Block: 1508643 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172769 RingCT/type: yes/0
Extra: 01a1a07b94a269324d2b882ddb1b5ff03298525a7af9162d4f52deb203d1338ba5021100000004e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 97663179f40aa467846bc40fd54f0daa743b210b69e29976e9a2b53e27a0f8c5 0.000600000000 1998397 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": 1508653, "vin": [ { "gen": { "height": 1508643 } } ], "vout": [ { "amount": 600000000, "target": { "key": "97663179f40aa467846bc40fd54f0daa743b210b69e29976e9a2b53e27a0f8c5" } } ], "extra": [ 1, 161, 160, 123, 148, 162, 105, 50, 77, 43, 136, 45, 219, 27, 95, 240, 50, 152, 82, 90, 122, 249, 22, 45, 79, 82, 222, 178, 3, 209, 51, 139, 165, 2, 17, 0, 0, 0, 4, 228, 245, 25, 63, 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: