← previous blocknext block →recent activity
Analyzing
Block #99,625,886
36 transactions · 25 stateful · 2026-08-27 13:30:24 UTC
Parallelism
81/100
Blocked
60%
Avg conflicts / tx
0.83
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #99,625,886 · 36 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w07w09w010w116w017w118w020w122w223w324w125w226w328w129w430w231w132w333w534w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x96ed54e2…04ed
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x21a85c1d…339a
0xd32edf…ff58
7 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x8548c2a9…baf2
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x5ab3fb12…8e76
0x34b655…2a6f
4 touches
1 conflict
0x9c168b41…7486
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 0x96ed54e2c0…a704ed
Audit this contract →
← previous block·next block →recent activity