← previous blocknext block →recent activity
Analyzing
Block #101,801,107
15 transactions · 15 stateful · 2026-09-04 04:06:54 UTC
Parallelism
67/100
Blocked
47%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,801,107 · 15 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w36w111w012w113w214w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb40e601f…bf98
0x34b655…2a6f
8 touches
6 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
8 touches
6 conflicts
0x3d13406e…eff1
0x34b655…2a6f
8 touches
6 conflicts
0x02372d42…1871
0x34b655…2a6f
8 touches
6 conflicts
0x3027f5b0…7a3f
0x34b655…2a6f
8 touches
6 conflicts
0x51fc8795…126f
0x34b655…2a6f
8 touches
6 conflicts
0x53e08444…d671
0x34b655…2a6f
8 touches
6 conflicts
0xe8f860c0…35c9
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 0xb40e601fc3…8bbf98
Audit this contract →
← previous block·next block →recent activity