← previous blocknext block →recent activity
Analyzing
Block #108,482,388
24 transactions · 22 stateful · 2026-09-27 13:54:37 UTC
Parallelism
83/100
Blocked
36%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #108,482,388 · 24 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
4w05w112w013w114w215w316w017w118w219w320w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x427aa12f…e796
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x797c4391…6833
0x34b655…2a6f
8 touches
6 conflicts
0xf30b9357…2e1e
0x34b655…2a6f
8 touches
6 conflicts
0x3d93ad2c…e747
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0xaad6be10…0801
0x2a68ba…90c5
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
6 conflicts on slot 0x427aa12f02…63e796
Audit this contract →
← previous block·next block →recent activity