← previous blocknext block →recent activity
Analyzing
Block #102,110,483
16 transactions · 12 stateful · 2026-09-05 06:11:59 UTC
Parallelism
81/100
Blocked
42%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,110,483 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w16w110w011w112w213w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x56ebd9dc…4917
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641d
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0x290abc80…f605
0x34b655…2a6f
6 touches
3 conflicts
0xf1894e7f…30fe
0x34b655…2a6f
6 touches
3 conflicts
0xf53ec6f6…7542
0x34b655…2a6f
5 touches
3 conflicts
0xba5743c7…21c4
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
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: Perpl
3 conflicts on slot 0x56ebd9dc0a…ee4917
Audit this contract →
← previous block·next block →recent activity