← previous blocknext block →recent activity
Analyzing
Block #101,966,198
15 transactions · 13 stateful · 2026-09-04 18:00:30 UTC
Parallelism
80/100
Blocked
38%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,966,198 · 15 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
1w03w14w27w111w012w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf139b130…d132
0x34b655…2a6f
4 touches
1 conflict
0xe4dce70d…2e50
0x34b655…2a6f
4 touches
1 conflict
0x0110331c…b891
0x34b655…2a6f
4 touches
1 conflict
0x33b7fbba…64de
0x34b655…2a6f
4 touches
1 conflict
0x36d57732…26f7
0x34b655…2a6f
4 touches
1 conflict
0x3a02129f…9eaf
0x34b655…2a6f
4 touches
1 conflict
0x3d4a3f35…7dc9
0x34b655…2a6f
4 touches
1 conflict
0x448fdf2a…fab4
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 0xf139b130f5…fdd132
Audit this contract →
← previous block·next block →recent activity