← previous blocknext block →recent activity
Analyzing
Block #108,942,193
25 transactions · 20 stateful · 2026-09-29 04:33:05 UTC
Parallelism
84/100
Blocked
40%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #108,942,193 · 25 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
4w05w17w08w012w113w014w115w216w117w218w224w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1ef2d9c5…8c0f
0x34b655…2a6f
6 touches
3 conflicts
0xbae4880a…306f
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x21c27d06…c469
0x34b655…2a6f
4 touches
1 conflict
0x3cb7ee74…b8a5
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x8b780b26…f5ff
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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 0x1ef2d9c5ba…a58c0f
Audit this contract →
← previous block·next block →recent activity