← previous blocknext block →recent activity
Analyzing
Block #99,155,943
25 transactions · 17 stateful · 2026-08-25 21:57:56 UTC
Parallelism
76/100
Blocked
41%
Avg conflicts / tx
0.64
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,155,943 · 25 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w112w016w118w121w222w323w424w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe1c4e5ce…0dec
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x4c29ecd5…58b6
0x34b655…2a6f
8 touches
6 conflicts
0xbd590df7…9891
0x34b655…2a6f
8 touches
6 conflicts
0xb0f5d668…99ac
0x34b655…2a6f
8 touches
6 conflicts
0xff38b4dd…8268
0x34b655…2a6f
6 touches
3 conflicts
0x6974210b…154c
0x34b655…2a6f
5 touches
3 conflicts
0x16d77246…bac5
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: Perpl
10 conflicts on slot 0xe1c4e5ce15…770dec
Audit this contract →
← previous block·next block →recent activity