← previous blocknext block →recent activity
Analyzing
Block #108,532,290
24 transactions · 22 stateful · 2026-09-27 18:05:50 UTC
Parallelism
75/100
Blocked
45%
Avg conflicts / tx
0.63
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #108,532,290 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w09w111w012w113w215w316w417w521w122w223w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6d955786…1327
0x34b655…2a6f
8 touches
6 conflicts
0x46b187cb…1733
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0xbe8ed88f…8084
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x3f5831e5…02b2
0x34b655…2a6f
6 touches
3 conflicts
0x54e6d2a8…ec22
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
6 conflicts on slot 0x6d95578697…071327
Audit this contract →
← previous block·next block →recent activity