← previous blocknext block →recent activity
Analyzing
Block #108,517,045
21 transactions · 20 stateful · 2026-09-27 16:49:07 UTC
Parallelism
71/100
Blocked
25%
Avg conflicts / tx
0.76
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #108,517,045 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w013w114w215w316w419w020w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5dc501b…831c
0x34b655…2a6f
12 touches
15 conflicts
0x7bd229ad…63b2
0x34b655…2a6f
12 touches
15 conflicts
0x1f84ce8a…5acc
0x34b655…2a6f
6 touches
3 conflicts
0xf8599ea8…874d
0x34b655…2a6f
4 touches
1 conflict
0x190b178a…c154
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x830d2293…1f51
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
15 conflicts on slot 0xf5dc501bf7…74831c
Audit this contract →
← previous block·next block →recent activity