← previous blocknext block →recent activity
Analyzing
Block #108,433,831
21 transactions · 17 stateful · 2026-09-27 09:50:12 UTC
Parallelism
81/100
Blocked
41%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #108,433,831 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w07w08w19w112w013w114w215w316w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa03c2a35…52e6
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0xcb45d9d6…cb83
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001b
0x1b6862…e19c
6 touches
3 conflicts
0xef4a76e5…4fe7
0x34b655…2a6f
6 touches
3 conflicts
0x2758a7db…8eb3
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
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 0xa03c2a355d…ca52e6
Audit this contract →
← previous block·next block →recent activity