← previous blocknext block →recent activity
Analyzing
Block #101,840,438
16 transactions · 16 stateful · 2026-09-04 07:24:43 UTC
Parallelism
75/100
Blocked
38%
Avg conflicts / tx
0.69
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,840,438 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w06w07w18w19w210w214w015w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x736b9166…5ea5
0x34b655…2a6f
8 touches
6 conflicts
0x0b0611f7…e63a
0x34b655…2a6f
4 touches
1 conflict
0x1a2055c7…9054
0x34b655…2a6f
4 touches
1 conflict
0x2f72db52…1c6e
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x640c4fb2…044a
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x74e46435…fdcd
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
6 conflicts on slot 0x736b916691…db5ea5
Audit this contract →
← previous block·next block →recent activity