← previous blocknext block →recent activity
Analyzing
Block #99,290,659
11 transactions · 10 stateful · 2026-08-26 09:15:46 UTC
Parallelism
82/100
Blocked
20%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,290,659 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w19w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x961c0cd9…0937
0x34b655…2a6f
4 touches
1 conflict
0xdc6a8e4b…d6f8
0x34b655…2a6f
4 touches
1 conflict
0x0fd2cbc5…476b
0x77d53b…8080
4 touches
1 conflict
0x195a0138…eade
0x77d53b…8080
4 touches
1 conflict
0x22d9df6d…76b0
0x77d53b…8080
4 touches
1 conflict
0x467e524d…39aa
0x77d53b…8080
4 touches
1 conflict
0x467e524d…39c9
0x77d53b…8080
4 touches
1 conflict
0x7e32f1e0…5612
0x77d53b…8080
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
1 conflict on slot 0x961c0cd92c…d10937
Audit this contract →
← previous block·next block →recent activity