← previous blocknext block →recent activity
Analyzing
Block #99,195,414
15 transactions · 15 stateful · 2026-08-26 01:16:31 UTC
Parallelism
73/100
Blocked
40%
Avg conflicts / tx
0.8
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,195,414 · 15 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w06w310w111w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0003
0x0a4fcb…a602
8 touches
6 conflicts
0x2b936aa5…05e5
0x141b1d…9583
8 touches
6 conflicts
0x00000000…0001
0x67d1be…196f
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x11258774…9892
0x2a68ba…90c5
4 touches
1 conflict
0xef949fe0…dc0a
0x065c9d…c394
4 touches
1 conflict
0x17f0f43c…2a5a
0x065c9d…c394
3 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: 0x0a4fcba9…7ba602
6 conflicts on slot 0x0000000000…000003
Audit this contract →
← previous block·next block →recent activity