← previous blocknext block →recent activity
Analyzing
Block #108,627,346
27 transactions · 24 stateful · 2026-09-28 02:04:34 UTC
Parallelism
81/100
Blocked
46%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,627,346 · 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
4w05w09w110w211w312w413w014w115w216w317w118w119w225w026w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5e2ea201…12de
0x34b655…2a6f
8 touches
6 conflicts
0xdaf02dea…dbd8
0x34b655…2a6f
8 touches
6 conflicts
0x43e3decb…be40
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x8639108d…59ad
0x34b655…2a6f
6 touches
3 conflicts
0x37c3f05c…f40b
0x34b655…2a6f
6 touches
3 conflicts
0xf35dca9e…bd8f
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
6 conflicts on slot 0x5e2ea201dc…2012de
Audit this contract →
← previous block·next block →recent activity