← previous blocknext block →recent activity
Analyzing
Block #99,288,311
21 transactions · 20 stateful · 2026-08-26 09:03:57 UTC
Parallelism
81/100
Blocked
35%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,288,311 · 21 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
4w05w17w08w19w214w116w217w018w119w020w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0fd2cbc5…476b
0x77d53b…8080
4 touches
1 conflict
0x7e32f1e0…5612
0x77d53b…8080
4 touches
1 conflict
0x85c42e7e…1a11
0x77d53b…8080
4 touches
1 conflict
0xe3abe489…ebf2
0x77d53b…8080
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xc8ab31f9…8ce9
0xa6afd3…d132
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x631b4113…baa9
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: 0x77d53b3b…378080
1 conflict on slot 0x0fd2cbc574…1c476b
Audit this contract →
← previous block·next block →recent activity