← previous blocknext block →recent activity
Analyzing
Block #107,651,449
19 transactions · 16 stateful · 2026-09-24 16:11:11 UTC
Parallelism
79/100
Blocked
31%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #107,651,449 · 19 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w09w110w211w314w015w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd52703e7…e17a
0x34b655…2a6f
8 touches
6 conflicts
0xd781b79e…fc2a
0x34b655…2a6f
6 touches
3 conflicts
0x98cc7c56…eab6
0x34b655…2a6f
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0x3d93ad2c…e747
0x34b655…2a6f
4 touches
1 conflict
0x7462b8f2…6312
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xcfe06a18…b5b5
0x34ae4d…3fc5
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
6 conflicts on slot 0xd52703e7ca…4fe17a
Audit this contract →
← previous block·next block →recent activity