← previous blocknext block →recent activity
Analyzing
Block #98,070,437
20 transactions · 15 stateful · 2026-08-22 02:12:38 UTC
Parallelism
90/100
Blocked
27%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,070,437 · 20 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
2w03w17w09w111w013w117w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5e8
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x62811193…186d
0x2b46c0…1669
2 touches
0 conflicts
0x62811193…186e
0x2b46c0…1669
2 touches
0 conflicts
0x7a12283f…b18a
0x2b46c0…1669
2 touches
0 conflicts
0x7a89325a…d7e0
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 0xe5bb3628b5…71e5e8
Audit this contract →
← previous block·next block →recent activity