← previous blocknext block →recent activity
Analyzing
Block #100,633,522
23 transactions · 19 stateful · 2026-08-31 02:12:19 UTC
Parallelism
78/100
Blocked
37%
Avg conflicts / tx
0.61
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,633,522 · 23 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
8w09w010w011w113w116w117w218w320w021w322w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x16ebf93b…ce00
0x34b655…2a6f
8 touches
6 conflicts
0xead15497…1dbe
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x38211058…7859
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 0x16ebf93bf3…87ce00
Audit this contract →
← previous block·next block →recent activity