← previous blocknext block →recent activity
Analyzing
Block #99,493,639
17 transactions · 17 stateful · 2026-08-27 02:17:43 UTC
Parallelism
88/100
Blocked
18%
Avg conflicts / tx
0.24
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,493,639 · 17 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
6w09w010w011w112w115w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd94e4cd9…b817
0x8964d7…10f8
4 touches
1 conflict
0x9cd55081…7bdf
0x8964d7…10f8
4 touches
1 conflict
0x9cd55081…7be0
0x8964d7…10f8
4 touches
1 conflict
0x9cd55081…7be1
0x8964d7…10f8
4 touches
1 conflict
0xd94e4cd9…b814
0x8964d7…10f8
4 touches
1 conflict
0xd94e4cd9…b815
0x8964d7…10f8
4 touches
1 conflict
0x6f132c01…cdcc
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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: 0x8964d7c9…5b10f8
1 conflict on slot 0xd94e4cd94f…e2b817
Audit this contract →
← previous block·next block →recent activity