← previous blocknext block →recent activity
Analyzing
Block #108,469,942
11 transactions · 11 stateful · 2026-09-27 12:51:58 UTC
Parallelism
73/100
Blocked
27%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #108,469,942 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe3254525…23a6
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x579441d4…249b
0x34b655…2a6f
4 touches
1 conflict
0x825d47fe…18fa
0x34b655…2a6f
4 touches
1 conflict
0xab52a7ec…2bcc
0x34b655…2a6f
4 touches
1 conflict
0xb40bfb34…5089
0x34b655…2a6f
4 touches
1 conflict
0xbc3d4a55…9228
0x34b655…2a6f
4 touches
1 conflict
0xc856ff11…2b9c
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
1 conflict on slot 0xe325452535…1623a6
Audit this contract →
← previous block·next block →recent activity