← previous blocknext block →recent activity
Analyzing
Block #101,841,881
18 transactions · 17 stateful · 2026-09-04 07:31:59 UTC
Parallelism
67/100
Blocked
53%
Avg conflicts / tx
0.78
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #101,841,881 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w15w07w28w19w214w315w116w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x736b9166…5ea5
0x34b655…2a6f
6 touches
3 conflicts
0x20b1228b…2487
0x34b655…2a6f
6 touches
3 conflicts
0x6aa6cc97…75ce
0x34b655…2a6f
4 touches
1 conflict
0x832e0586…84e7
0x34b655…2a6f
4 touches
1 conflict
0x995dd5a8…ce9c
0x34b655…2a6f
4 touches
1 conflict
0x9e70dadd…810d
0x34b655…2a6f
4 touches
1 conflict
0xa9988419…9f45
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity