← previous blocknext block →recent activity
Analyzing
Block #99,284,629
19 transactions · 18 stateful · 2026-08-26 08:45:26 UTC
Parallelism
89/100
Blocked
11%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,284,629 · 19 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
4w016w017w118w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x631b4113…baa9
0x34b655…2a6f
4 touches
1 conflict
0x0fd2cbc5…476b
0x77d53b…8080
4 touches
1 conflict
0x29f3d595…de93
0x77d53b…8080
4 touches
1 conflict
0x467e524d…39c9
0x77d53b…8080
4 touches
1 conflict
0x85c42e7e…1a0a
0x77d53b…8080
4 touches
1 conflict
0x85c42e7e…1a10
0x77d53b…8080
4 touches
1 conflict
0x85c42e7e…1a11
0x77d53b…8080
4 touches
1 conflict
0x85c42e7e…1a16
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 0x631b41138f…31baa9
Audit this contract →
← previous block·next block →recent activity