← previous blocknext block →recent activity
Analyzing
Block #98,740,398
18 transactions · 15 stateful · 2026-08-24 11:00:14 UTC
Parallelism
89/100
Blocked
7%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,740,398 · 18 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
16w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fbc2e5a…e69c
0x34b655…2a6f
4 touches
1 conflict
0x4ccffab5…074b
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x7e17e82a…9748
0x34b655…2a6f
3 touches
1 conflict
0x20e2f653…f776
0x34b655…2a6f
2 touches
0 conflicts
0x29cac3f0…d958
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 0x6fbc2e5a11…b3e69c
Audit this contract →
← previous block·next block →recent activity