Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3fa68c074a4ef8f3707bca9a84c0d356f85c7d27c68956b1f7dc293960e48ee8

Tx prefix hash: 45d282af059dccfff53d7c5c6a3e4b9c1e100ef8baf54fa0d0979223c7653abb
Tx public key: 349e9de46314d96c2157c502fcec04d2d518803c1ba77c051e41435242980258
Timestamp: 1691991245 Timestamp [UTC]: 2023-08-14 05:34:05 Age [y:d:h:m:s]: 02:270:00:04:10
Block: 825506 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 705368 RingCT/type: yes/0
Extra: 01349e9de46314d96c2157c502fcec04d2d518803c1ba77c051e41435242980258021100000006e6d27f9c000000000000000000

1 output(s) for total of 0.001129161419 xmr

stealth address amount amount idx tag
00: 0f4aa71f792ab0d59a5ab2d6dbd344e14da6e38554b9d45e1d6a0d90182ce6ca 0.001129161419 1277760 of 0 -

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": 825516, "vin": [ { "gen": { "height": 825506 } } ], "vout": [ { "amount": 1129161419, "target": { "key": "0f4aa71f792ab0d59a5ab2d6dbd344e14da6e38554b9d45e1d6a0d90182ce6ca" } } ], "extra": [ 1, 52, 158, 157, 228, 99, 20, 217, 108, 33, 87, 197, 2, 252, 236, 4, 210, 213, 24, 128, 60, 27, 167, 124, 5, 30, 65, 67, 82, 66, 152, 2, 88, 2, 17, 0, 0, 0, 6, 230, 210, 127, 156, 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: