← previous blocknext block →recent activity
Analyzing
Block #108,351,226
24 transactions · 20 stateful · 2026-09-27 02:54:29 UTC
Parallelism
79/100
Blocked
35%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,351,226 · 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
13w014w115w216w017w118w219w320w421w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa0998a89…1f5a
0x34b655…2a6f
10 touches
10 conflicts
0xba1edffb…323e
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0xbac338fb…5aec
0x34b655…2a6f
8 touches
6 conflicts
0xcb21158b…f18d
0x34b655…2a6f
8 touches
6 conflicts
0x5ad5e6de…e7ad
0x34b655…2a6f
2 touches
0 conflicts
0xe226a0be…c046
0x34b655…2a6f
2 touches
0 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: Perpl
10 conflicts on slot 0xa0998a8998…e71f5a
Audit this contract →
← previous block·next block →recent activity