← previous blocknext block →recent activity
Analyzing
Block #100,106,656
18 transactions · 18 stateful · 2026-08-29 05:57:18 UTC
Parallelism
61/100
Blocked
56%
Avg conflicts / tx
1.17
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,106,656 · 18 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
1w02w04w15w26w38w110w211w412w513w014w115w117w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbee5cfda…5e91
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x7d0eaae2…60b7
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x50812214…4dcd
0x34b655…2a6f
4 touches
1 conflict
0x5ecbbe42…e861
0x34b655…2a6f
4 touches
1 conflict
0x5ed1f9d0…fc7f
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
10 conflicts on slot 0xbee5cfda6a…2c5e91
Audit this contract →
← previous block·next block →recent activity