← previous blocknext block →recent activity
Analyzing
Block #102,243,789
24 transactions · 17 stateful · 2026-09-05 17:27:34 UTC
Parallelism
79/100
Blocked
35%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,243,789 · 24 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
9w010w011w012w116w119w220w221w322w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa9d11061…b7e9
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6426
0x34b655…2a6f
6 touches
3 conflicts
0x224806ab…af9e
0x34b655…2a6f
6 touches
3 conflicts
0x3c9d1d97…0401
0xd32edf…ff58
5 touches
3 conflicts
0x2aa6ddc7…e298
0x34b655…2a6f
4 touches
1 conflict
0x2fc7853f…2c85
0x34b655…2a6f
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
10 conflicts on slot 0xa9d110613e…d3b7e9
Audit this contract →
← previous block·next block →recent activity