← previous blocknext block →recent activity
Analyzing
Block #98,537,508
10 transactions · 9 stateful · 2026-08-23 17:30:45 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,537,508 · 10 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
2w04w06w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2cef1eff…9f14
0x34b655…2a6f
4 touches
1 conflict
0xb3a15862…d092
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x14cc77c7…69c4
0x34b655…2a6f
2 touches
0 conflicts
0x5a7d6ae7…8f82
0x34b655…2a6f
2 touches
0 conflicts
0x711ed6c5…cebb
0x34b655…2a6f
2 touches
0 conflicts
0x8641bdc9…7e57
0x34b655…2a6f
2 touches
0 conflicts
0x9b862e76…e3c2
0x34b655…2a6f
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 0x2cef1eff78…339f14
Audit this contract →
← previous block·next block →recent activity