← previous blocknext block →recent activity
Analyzing
Block #108,501,819
18 transactions · 17 stateful · 2026-09-27 15:32:28 UTC
Parallelism
72/100
Blocked
29%
Avg conflicts / tx
0.39
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,501,819 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w212w214w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc6c4afb7…5c29
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x4c29ecd5…58b6
0x34b655…2a6f
6 touches
3 conflicts
0x40d6d1e9…131e
0x34b655…2a6f
4 touches
1 conflict
0x5969523e…5191
0x34b655…2a6f
4 touches
1 conflict
0x5fa6e1a0…c881
0x34b655…2a6f
4 touches
1 conflict
0x7006165a…df17
0x34b655…2a6f
4 touches
1 conflict
0x8eac5088…e823
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
3 conflicts on slot 0xc6c4afb72d…9f5c29
Audit this contract →
← previous block·next block →recent activity