← previous blocknext block →recent activity
Analyzing
Block #98,444,045
81 transactions · 80 stateful · 2026-08-23 09:33:02 UTC
Parallelism
98/100
Blocked
3%
Avg conflicts / tx
0.02
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,444,045 · 81 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w19w078w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec7d4774…8b1c
0x34b655…2a6f
4 touches
1 conflict
0xf48fa71e…bb52
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x2f74f175…9286
0x2b46c0…1669
2 touches
0 conflicts
0x2f74f175…9287
0x2b46c0…1669
2 touches
0 conflicts
0x2f74f175…9288
0x2b46c0…1669
2 touches
0 conflicts
0x2f74f175…9289
0x2b46c0…1669
2 touches
0 conflicts
0x3ba7edbb…80e6
0x2b46c0…1669
2 touches
0 conflicts
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 0xec7d4774db…558b1c
Audit this contract →
← previous block·next block →recent activity