← previous blocknext block →recent activity
Analyzing
Block #101,893,039
17 transactions · 17 stateful · 2026-09-04 11:49:26 UTC
Parallelism
82/100
Blocked
29%
Avg conflicts / tx
0.53
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,893,039 · 17 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
1w02w13w04w09w110w211w215w016w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x98e2f231…ab6e
0x34b655…2a6f
6 touches
3 conflicts
0x01315072…0e2d
0x34b655…2a6f
4 touches
1 conflict
0x04d4f30d…4dfb
0x34b655…2a6f
4 touches
1 conflict
0x0d19cd25…a3c2
0x34b655…2a6f
4 touches
1 conflict
0x29a58269…011a
0x34b655…2a6f
4 touches
1 conflict
0x38276446…2aa9
0x34b655…2a6f
4 touches
1 conflict
0x3d13406e…eff1
0x34b655…2a6f
4 touches
1 conflict
0x477cb4f5…11b4
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 0x98e2f23176…02ab6e
Audit this contract →
← previous block·next block →recent activity