← previous blocknext block →recent activity
Analyzing
Block #100,788,064
26 transactions · 21 stateful · 2026-08-31 15:09:52 UTC
Parallelism
81/100
Blocked
33%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,788,064 · 26 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
12w013w114w015w218w019w120w321w423w024w125w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4de98788…170c
0x34b655…2a6f
10 touches
10 conflicts
0x5d1ac445…5233
0x34b655…2a6f
8 touches
6 conflicts
0x42e917f7…ed8c
0x34b655…2a6f
6 touches
3 conflicts
0x8ff85b19…dde0
0x34b655…2a6f
6 touches
3 conflicts
0xb4ee3c39…0f88
0x40c49f…2af0
4 touches
1 conflict
0x825a1cb0…11fc
0x34b655…2a6f
4 touches
1 conflict
0x898d9b8a…d1ef
0x34b655…2a6f
4 touches
1 conflict
0x9482a067…eba9
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 0x4de98788fa…a2170c
Audit this contract →
← previous block·next block →recent activity