← previous blocknext block →recent activity
Analyzing
Block #100,732,063
18 transactions · 18 stateful · 2026-08-31 10:28:00 UTC
Parallelism
72/100
Blocked
44%
Avg conflicts / tx
0.61
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,732,063 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w15w06w07w111w212w313w214w115w417w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x24b08f9c…e594
0x34b655…2a6f
6 touches
3 conflicts
0x89ac61bf…9443
0x34b655…2a6f
6 touches
3 conflicts
0x9ad82ccb…b08b
0x34b655…2a6f
6 touches
3 conflicts
0x092be5df…d67e
0x34b655…2a6f
5 touches
3 conflicts
0x54c6fb44…369a
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xa952c504…7b64
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
3 conflicts on slot 0x24b08f9c98…6ae594
Audit this contract →
← previous block·next block →recent activity