← previous blocknext block →recent activity
Analyzing
Block #100,605,802
20 transactions · 16 stateful · 2026-08-30 23:52:53 UTC
Parallelism
65/100
Blocked
63%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,605,802 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w16w27w38w110w112w213w414w518w319w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x5ed1f9d0…fc7f
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x451e482b…7e7d
0x34b655…2a6f
4 touches
1 conflict
0x63e19f54…7853
0x34b655…2a6f
4 touches
1 conflict
0x8dcb756a…3fe4
0x34b655…2a6f
4 touches
1 conflict
0xa11b60f7…8e8b
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
6 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity