← previous blocknext block →recent activity
Analyzing
Block #101,017,085
20 transactions · 19 stateful · 2026-09-01 10:22:13 UTC
Parallelism
80/100
Blocked
32%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,017,085 · 20 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
1w02w19w010w111w212w314w015w117w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x07bb3f5a…617e
0x34b655…2a6f
8 touches
6 conflicts
0xdfaa9666…2003
0x34b655…2a6f
8 touches
6 conflicts
0x46f78cfd…3f67
0x34b655…2a6f
8 touches
6 conflicts
0xcd26fba5…21c6
0x34b655…2a6f
8 touches
6 conflicts
0x039ce85a…1c52
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x5e3014f0…b4e1
0x34b655…2a6f
4 touches
1 conflict
0xf79df061…e005
0xe52b14…7230
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 0x07bb3f5a12…2d617e
Audit this contract →
← previous block·next block →recent activity