← previous blocknext block →recent activity
Analyzing
Block #100,031,387
17 transactions · 15 stateful · 2026-08-28 23:38:23 UTC
Parallelism
76/100
Blocked
33%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,031,387 · 17 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
1w03w05w17w18w210w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8649d60a…16f6
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x2f835a56…0ded
0x34b655…2a6f
4 touches
1 conflict
0xf788c790…e66f
0x34b655…2a6f
4 touches
1 conflict
0x01e9f543…cb82
0x34b655…2a6f
4 touches
1 conflict
0x2f662f0a…f602
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
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 0x8649d60a20…bf16f6
Audit this contract →
← previous block·next block →recent activity