← previous blocknext block →recent activity
Analyzing
Block #99,320,645
19 transactions · 14 stateful · 2026-08-26 11:46:35 UTC
Parallelism
79/100
Blocked
43%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,320,645 · 19 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
1w02w13w04w15w26w07w110w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbeb716e1…2f28
0x34b655…2a6f
8 touches
6 conflicts
0xea2eef12…dd5a
0x34b655…2a6f
6 touches
3 conflicts
0x961c0cd9…0937
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001d
0x1b6862…e19c
4 touches
1 conflict
0xb550abea…2729
0x34b655…2a6f
4 touches
1 conflict
0x3af0dd8e…0026
0x1b6862…e19c
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
6 conflicts on slot 0xbeb716e153…892f28
Audit this contract →
← previous block·next block →recent activity