← previous blocknext block →recent activity
Analyzing
Block #108,509,776
14 transactions · 12 stateful · 2026-09-27 16:12:31 UTC
Parallelism
86/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #108,509,776 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w08w09w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbe0e5883…78f0
0x34b655…2a6f
4 touches
1 conflict
0xe1c4e5ce…0dec
0x34b655…2a6f
4 touches
1 conflict
0x4c29ecd5…58b6
0x34b655…2a6f
4 touches
1 conflict
0x5cd3006f…3d44
0x34b655…2a6f
4 touches
1 conflict
0x7f5fc95b…d9c0
0x065c9d…c394
2 touches
0 conflicts
0x972abc84…978e
0x065c9d…c394
2 touches
0 conflicts
0xc7debc3c…112b
0x065c9d…c394
2 touches
0 conflicts
0xaad6be10…0801
0x2a68ba…90c5
2 touches
0 conflicts
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 0xbe0e588347…5978f0
Audit this contract →
← previous block·next block →recent activity