← previous blocknext block →recent activity
Analyzing
Block #100,627,296
19 transactions · 16 stateful · 2026-08-31 01:41:00 UTC
Parallelism
74/100
Blocked
50%
Avg conflicts / tx
0.95
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,627,296 · 19 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
1w02w14w26w310w011w112w213w315w418w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc3d9b281…6231
0x34b655…2a6f
10 touches
10 conflicts
0x16ebf93b…ce00
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x17d0feef…8f30
0x34b655…2a6f
6 touches
3 conflicts
0xecd87a39…d9c5
0x34b655…2a6f
6 touches
3 conflicts
0xfe39a1f7…8eb0
0x34b655…2a6f
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x4e58deff…c5d0
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 0xc3d9b2819f…d06231
Audit this contract →
← previous block·next block →recent activity