← previous blocknext block →recent activity
Analyzing
Block #100,118,326
11 transactions · 11 stateful · 2026-08-29 06:56:05 UTC
Parallelism
64/100
Blocked
27%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,118,326 · 11 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
2w04w05w16w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x044844a0…7418
0x34b655…2a6f
6 touches
3 conflicts
0x672a4ed7…3f82
0x34b655…2a6f
6 touches
3 conflicts
0xa5811d93…8c73
0x34b655…2a6f
4 touches
1 conflict
0x12ea6b9f…260f
0x34b655…2a6f
4 touches
1 conflict
0xf788c790…e66f
0x34b655…2a6f
4 touches
1 conflict
0x43b2a3c0…34eb
0x34b655…2a6f
4 touches
1 conflict
0x50a71507…3b58
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
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 0x044844a0f0…d07418
Audit this contract →
← previous block·next block →recent activity