← previous blocknext block →recent activity
Analyzing
Block #101,991,559
14 transactions · 13 stateful · 2026-09-04 20:09:10 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,991,559 · 14 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
1w02w13w24w312w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc00be471…2449
0x34b655…2a6f
8 touches
6 conflicts
0x7daf6443…fd36
0x34b655…2a6f
6 touches
3 conflicts
0xc7bb912f…ad41
0x34b655…2a6f
6 touches
3 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
0xd609afa5…237c
0x34b655…2a6f
6 touches
3 conflicts
0x8e10b110…c501
0x34b655…2a6f
6 touches
3 conflicts
0xc0f6895c…e428
0x34b655…2a6f
6 touches
3 conflicts
0x8feb2121…031a
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 0xc00be47185…ae2449
Audit this contract →
← previous block·next block →recent activity