← previous blocknext block →recent activity
Analyzing
Block #108,952,089
26 transactions · 23 stateful · 2026-09-29 05:23:02 UTC
Parallelism
27/100
Blocked
83%
Avg conflicts / tx
5.58
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #108,952,089 · 26 txs across 19 waves · depth 19
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
wave w18
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w810w911w1012w1113w1214w615w1323w1625w18
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8b780b26…f5ff
0x34b655…2a6f
30 touches
105 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
28 touches
91 conflicts
0xca841faa…486a
0x34b655…2a6f
28 touches
91 conflicts
0x5ad5e6de…e7ad
0x34b655…2a6f
26 touches
78 conflicts
0x71f645aa…3afd
0x34b655…2a6f
26 touches
78 conflicts
0x7499cc33…a306
0x34b655…2a6f
26 touches
78 conflicts
0x88fc2a68…3918
0x34b655…2a6f
26 touches
78 conflicts
0x98dd86bb…1edb
0x34b655…2a6f
26 touches
78 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
105 conflicts on slot 0x8b780b2668…85f5ff
Audit this contract →
← previous block·next block →recent activity