← previous blocknext block →recent activity
Analyzing
Block #100,787,788
19 transactions · 18 stateful · 2026-08-31 15:08:29 UTC
Parallelism
68/100
Blocked
44%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,787,788 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w16w07w18w29w310w411w113w514w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0a523508…d9b0
0x34b655…2a6f
12 touches
15 conflicts
0x81716ce9…095f
0x34b655…2a6f
10 touches
10 conflicts
0xa9988419…9f45
0x34b655…2a6f
8 touches
6 conflicts
0x9f4801c8…0afe
0x34b655…2a6f
8 touches
6 conflicts
0x9210e826…1414
0x34b655…2a6f
8 touches
6 conflicts
0xd86a37ca…11c0
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 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
15 conflicts on slot 0x0a52350887…ded9b0
Audit this contract →
← previous block·next block →recent activity