← previous blocknext block →recent activity
Analyzing
Block #99,289,824
17 transactions · 16 stateful · 2026-08-26 09:11:34 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,289,824 · 17 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
4w05w18w210w111w213w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53ba0ad9…d8f5
0x34b655…2a6f
10 touches
10 conflicts
0xfaf89f45…ced6
0x34b655…2a6f
8 touches
6 conflicts
0x8a02d049…f481
0x34b655…2a6f
6 touches
3 conflicts
0xf51ec09c…b4a9
0x34b655…2a6f
4 touches
1 conflict
0xe283e878…7262
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x7b74ef7e…66b7
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
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 0x53ba0ad985…abd8f5
Audit this contract →
← previous block·next block →recent activity