Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3a8edff505d6801170c8535b1aebe89154f25549d7009773efced309bd0c1cf

Tx prefix hash: 38f9e5329faa2b91be72029274aee7c2091df17b46dce2427540827e44478c1a
Tx public key: 9f89eec898588876ae681de6cc34c74215433cf1e5ca8bbe07a0c35e1472b644
Timestamp: 1758181302 Timestamp [UTC]: 2025-09-18 07:41:42 Age [y:d:h:m:s]: 01:064:19:41:12
Block: 1370991 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 312503 RingCT/type: yes/0
Extra: 019f89eec898588876ae681de6cc34c74215433cf1e5ca8bbe07a0c35e1472b644021100000002ad7948d0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a0e9f3cbe6f27f22b23af79fc73a5ef4b027878961df0f68fa4b726943f5d587 0.000600000000 1859068 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": 1371001, "vin": [ { "gen": { "height": 1370991 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0e9f3cbe6f27f22b23af79fc73a5ef4b027878961df0f68fa4b726943f5d587" } } ], "extra": [ 1, 159, 137, 238, 200, 152, 88, 136, 118, 174, 104, 29, 230, 204, 52, 199, 66, 21, 67, 60, 241, 229, 202, 139, 190, 7, 160, 195, 94, 20, 114, 182, 68, 2, 17, 0, 0, 0, 2, 173, 121, 72, 208, 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: