← previous blocknext block →recent activity
Analyzing
Block #108,451,754
16 transactions · 13 stateful · 2026-09-27 11:20:26 UTC
Parallelism
81/100
Blocked
15%
Avg conflicts / tx
0.19
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #108,451,754 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w010w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc99d7f64…a643
0x34b655…2a6f
6 touches
3 conflicts
0x0a2b2926…5ff5
0x34b655…2a6f
4 touches
1 conflict
0x221e8974…2a9a
0x34b655…2a6f
4 touches
1 conflict
0xdf869f4c…dd52
0x34b655…2a6f
4 touches
1 conflict
0x4292a836…9ed5
0x34b655…2a6f
4 touches
1 conflict
0x06133cc3…37bf
0x34b655…2a6f
2 touches
0 conflicts
0x4c0a6381…e201
0x34b655…2a6f
2 touches
0 conflicts
0x625c4ed4…16aa
0x34b655…2a6f
2 touches
0 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
3 conflicts on slot 0xc99d7f648e…a5a643
Audit this contract →
← previous block·next block →recent activity