← previous blocknext block →recent activity
Analyzing
Block #108,960,942
33 transactions · 31 stateful · 2026-09-29 06:07:59 UTC
Parallelism
76/100
Blocked
42%
Avg conflicts / tx
1.06
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #108,960,942 · 33 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w16w19w110w211w212w313w414w515w616w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x516ac1cd…5392
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x72083f0d…082a
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x11b48164…0317
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x8b780b26…f5ff
0x34b655…2a6f
4 touches
1 conflict
0x941bd594…21fd
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
21 conflicts on slot 0x516ac1cdb7…e45392
Audit this contract →
← previous block·next block →recent activity