← previous blocknext block →recent activity
Analyzing
Block #99,181,662
23 transactions · 21 stateful · 2026-08-26 00:07:18 UTC
Parallelism
87/100
Blocked
33%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,181,662 · 23 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w08w09w010w013w215w116w118w120w021w122w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x7f91f4f0…52b4
0xd32edf…ff58
5 touches
3 conflicts
0xe488f7b4…8be6
0x34b655…2a6f
4 touches
1 conflict
0x07da3bda…cc3b
0x34b655…2a6f
4 touches
1 conflict
0x81716ce9…095f
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xe5e7089a…fb91
0x34b655…2a6f
4 touches
1 conflict
0xe9410c19…a5a4
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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity