← previous blocknext block →recent activity
Analyzing
Block #100,626,187
22 transactions · 19 stateful · 2026-08-31 01:35:25 UTC
Parallelism
82/100
Blocked
26%
Avg conflicts / tx
0.41
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,626,187 · 22 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w19w010w111w213w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca2b4ab7…5236
0x34b655…2a6f
8 touches
6 conflicts
0x731d7308…fd26
0x34b655…2a6f
6 touches
3 conflicts
0x9ff4ca89…6115
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd2a76d80…ee44
0x34b655…2a6f
4 touches
1 conflict
0x35c25a00…78ca
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 0xca2b4ab77a…6e5236
Audit this contract →
← previous block·next block →recent activity