← previous blocknext block →recent activity
Analyzing
Block #101,973,159
13 transactions · 13 stateful · 2026-09-04 18:35:44 UTC
Parallelism
77/100
Blocked
31%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,973,159 · 13 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
1w02w13w04w16w07w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0bd3f941…48ff
0x34b655…2a6f
4 touches
1 conflict
0x0ebdf9aa…7f66
0x34b655…2a6f
4 touches
1 conflict
0x1a22ba72…eeea
0x34b655…2a6f
4 touches
1 conflict
0x2aa7be4c…0f84
0x34b655…2a6f
4 touches
1 conflict
0x5c7b5ec0…0764
0x34b655…2a6f
4 touches
1 conflict
0x67043b0b…97d7
0x34b655…2a6f
4 touches
1 conflict
0x67c1f465…38b3
0x34b655…2a6f
4 touches
1 conflict
0x6c7c1a4b…5751
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
1 conflict on slot 0x0bd3f94190…1a48ff
Audit this contract →
← previous block·next block →recent activity