← previous blocknext block →recent activity
Analyzing
Block #100,562,061
24 transactions · 22 stateful · 2026-08-30 20:12:50 UTC
Parallelism
79/100
Blocked
41%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,562,061 · 24 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
3w04w05w17w28w211w313w214w119w422w323w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9d22c394…c125
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x39faf6fe…d786
0x34b655…2a6f
6 touches
3 conflicts
0xea57afd0…4232
0x34b655…2a6f
6 touches
3 conflicts
0x51087f5a…61f7
0x34b655…2a6f
4 touches
1 conflict
0x6183ee9a…21b1
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
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 0x9d22c394fb…48c125
Audit this contract →
← previous block·next block →recent activity