← previous blocknext block →recent activity
Analyzing
Block #100,630,393
12 transactions · 12 stateful · 2026-08-31 01:56:35 UTC
Parallelism
83/100
Blocked
8%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,630,393 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa5811d93…8c73
0x34b655…2a6f
4 touches
1 conflict
0xe720a4c6…8eb0
0x34b655…2a6f
4 touches
1 conflict
0x9e3aec8e…22d1
0x34b655…2a6f
4 touches
1 conflict
0x21e79ad8…c5db
0x34b655…2a6f
2 touches
0 conflicts
0x3243e72f…1f6d
0x34b655…2a6f
2 touches
0 conflicts
0x34dad526…5f98
0x34b655…2a6f
2 touches
0 conflicts
0x4a45b318…9716
0x34b655…2a6f
2 touches
0 conflicts
0x556beb43…e627
0x34b655…2a6f
2 touches
0 conflicts
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 0xa5811d93b4…4d8c73
Audit this contract →
← previous block·next block →recent activity