← previous blocknext block →recent activity
Analyzing
Block #108,960,431
29 transactions · 23 stateful · 2026-09-29 06:05:21 UTC
Parallelism
90/100
Blocked
26%
Avg conflicts / tx
0.28
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #108,960,431 · 29 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
4w05w16w08w09w114w115w016w117w125w026w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa0a8c7a5…3422
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xf9c55595…1607
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x21a4b688…0862
0x40c49f…2af0
4 touches
1 conflict
0x3f2ea619…3dbe
0x40c49f…2af0
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
3 conflicts on slot 0xa0a8c7a55a…e73422
Audit this contract →
← previous block·next block →recent activity