← previous blocknext block →recent activity
Analyzing
Block #108,467,086
20 transactions · 18 stateful · 2026-09-27 12:37:36 UTC
Parallelism
85/100
Blocked
33%
Avg conflicts / tx
0.35
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #108,467,086 · 20 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
1w02w05w06w19w011w112w115w017w118w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5dc501b…831c
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x215a6da4…0e86
0x34b655…2a6f
4 touches
1 conflict
0x235bbb77…89ea
0x34b655…2a6f
4 touches
1 conflict
0x301e1c77…9e30
0x34b655…2a6f
4 touches
1 conflict
0x3bb4491a…4aaf
0x34b655…2a6f
4 touches
1 conflict
0x47ee9f76…8dee
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 0xf5dc501bf7…74831c
Audit this contract →
← previous block·next block →recent activity