← previous blocknext block →recent activity
Analyzing
Block #102,205,543
27 transactions · 25 stateful · 2026-09-05 14:13:50 UTC
Parallelism
81/100
Blocked
56%
Avg conflicts / tx
1.11
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,205,543 · 27 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w07w18w09w210w011w312w013w414w015w116w217w326w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5b0621ee…3c2c
0x284f45…7777
10 touches
10 conflicts
0xd868fb65…3b4a
0xe1c8b7…3022
10 touches
10 conflicts
0xa164d951…1534
0xe1c8b7…3022
10 touches
10 conflicts
0x00000000…0004
0x7aed55…0617
10 touches
10 conflicts
0xdf409966…6b16
0x3bd359…433a
10 touches
10 conflicts
0x4eb758b8…b13b
0x3bd359…433a
10 touches
10 conflicts
0x44ed742f…63f5
0x3bd359…433a
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: 0x284f45fa…de7777
10 conflicts on slot 0x5b0621ee5a…623c2c
Audit this contract →
← previous block·next block →recent activity