← previous blocknext block →recent activity
Analyzing
Block #99,614,802
17 transactions · 17 stateful · 2026-08-27 12:33:22 UTC
Parallelism
71/100
Blocked
35%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,614,802 · 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
2w04w06w17w09w210w011w012w113w314w115w016w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xee7c63cc…88de
0x851145…3f07
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x348fda08…7e96
0x065c9d…c394
4 touches
1 conflict
0x021cd478…a6d4
0x34b655…2a6f
4 touches
1 conflict
0x021ee029…36ee
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x3e49348b…9445
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: 0x851145ea…9f3f07
1 conflict on slot 0xee7c63ccb6…9f88de
Audit this contract →
← previous block·next block →recent activity