← previous blocknext block →recent activity
Analyzing
Block #108,684,488
30 transactions · 24 stateful · 2026-09-28 06:52:23 UTC
Parallelism
87/100
Blocked
42%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #108,684,488 · 30 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
1w02w13w04w15w010w012w114w015w116w219w321w322w224w125w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb9868b52…c77f
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ef403…70a3
0x34b655…2a6f
6 touches
3 conflicts
0xa11bd7ea…20b4
0x34b655…2a6f
6 touches
3 conflicts
0xba9f88e8…9c33
0x34b655…2a6f
6 touches
3 conflicts
0xbb461ef2…c57b
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0xb9868b5233…c6c77f
Audit this contract →
← previous block·next block →recent activity