← previous blocknext block →recent activity
Analyzing
Block #99,491,378
14 transactions · 14 stateful · 2026-08-27 02:06:20 UTC
Parallelism
86/100
Blocked
21%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,491,378 · 14 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
2w05w09w110w011w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6c3870ae…264d
0x8964d7…10f8
4 touches
1 conflict
0x36f538e5…4706
0x8964d7…10f8
4 touches
1 conflict
0x36f538e5…4707
0x8964d7…10f8
4 touches
1 conflict
0x6c3870ae…264a
0x8964d7…10f8
4 touches
1 conflict
0x6c3870ae…264b
0x8964d7…10f8
4 touches
1 conflict
0x00500a94…20d5
0x34b655…2a6f
4 touches
1 conflict
0x1adc4533…810b
0x34b655…2a6f
4 touches
1 conflict
0x5c455afd…ce06
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 0x6c3870aec5…32264d
Audit this contract →
← previous block·next block →recent activity