← previous blocknext block →recent activity
Analyzing
Block #99,984,254
36 transactions · 36 stateful · 2026-08-28 19:41:03 UTC
Parallelism
86/100
Blocked
19%
Avg conflicts / tx
0.47
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,984,254 · 36 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
3w05w16w27w39w010w131w232w333w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa11b60f7…8e8b
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xeff238b4…7296
0x34b655…2a6f
4 touches
1 conflict
0xffc2f763…10b1
0x34b655…2a6f
4 touches
1 conflict
0x35b0198e…3e0d
0x34b655…2a6f
4 touches
1 conflict
0x29354600…7b17
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
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 0xa11b60f7c7…f88e8b
Audit this contract →
← previous block·next block →recent activity