← previous blocknext block →recent activity
Analyzing
Block #99,210,526
18 transactions · 17 stateful · 2026-08-26 02:32:32 UTC
Parallelism
83/100
Blocked
24%
Avg conflicts / tx
0.39
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,210,526 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w17w010w012w115w016w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x175b4ad7…70f7
0x8964d7…10f8
4 touches
1 conflict
0x175b4ad7…70f5
0x8964d7…10f8
4 touches
1 conflict
0x175b4ad7…70f4
0x8964d7…10f8
4 touches
1 conflict
0x175b4ad7…70f1
0x8964d7…10f8
4 touches
1 conflict
0x175b4ad7…70f0
0x8964d7…10f8
4 touches
1 conflict
0x00000000…0008
0x8964d7…10f8
4 touches
1 conflict
0x2a07e64e…fe77
0x754704…b603
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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity