← previous blocknext block →recent activity
Analyzing
Block #108,587,371
18 transactions · 14 stateful · 2026-09-27 22:43:18 UTC
Parallelism
89/100
Blocked
14%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #108,587,371 · 18 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6951608c…77cd
0x34b655…2a6f
4 touches
1 conflict
0x7bd229ad…63b2
0x34b655…2a6f
4 touches
1 conflict
0xf5dc501b…831c
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x0311862a…7c5c
0x34b655…2a6f
4 touches
1 conflict
0x8d44323d…0250
0x34b655…2a6f
2 touches
0 conflicts
0xa6ae5ca5…0fab
0x34b655…2a6f
2 touches
0 conflicts
0xaa61fe45…2c48
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
1 conflict on slot 0x6951608c7a…1477cd
Audit this contract →
← previous block·next block →recent activity