← previous blocknext block →recent activity
Analyzing
Block #99,857,494
15 transactions · 14 stateful · 2026-08-28 09:02:17 UTC
Parallelism
73/100
Blocked
29%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,857,494 · 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
1w02w16w010w111w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xab5bf10e…9f88
0x34b655…2a6f
8 touches
6 conflicts
0x706c758c…2fdb
0x34b655…2a6f
6 touches
3 conflicts
0xcef70a96…db44
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0018
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0028
0x1b6862…e19c
4 touches
1 conflict
0x6c6f37ba…c205
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 0xab5bf10ef0…ab9f88
Audit this contract →
← previous block·next block →recent activity