← previous blocknext block →recent activity
Analyzing
Block #98,432,117
56 transactions · 45 stateful · 2026-08-23 08:33:01 UTC
Parallelism
95/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,432,117 · 56 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
12w013w014w115w016w117w018w122w123w024w254w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xee132cc0…51ef
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x9e1c65d0…77a3
0x34b655…2a6f
4 touches
1 conflict
0x5778d110…d2e6
0xc8689a…ee79
4 touches
1 conflict
0xe5bb3628…e5f1
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
1 conflict on slot 0xee132cc0bf…1851ef
Audit this contract →
← previous block·next block →recent activity