← previous blocknext block →recent activity
Analyzing
Block #98,594,619
15 transactions · 15 stateful · 2026-08-23 22:28:42 UTC
Parallelism
67/100
Blocked
40%
Avg conflicts / tx
0.73
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,594,619 · 15 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w07w19w210w312w413w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x398e1fec…f13e
0x34b655…2a6f
6 touches
3 conflicts
0xcc347471…02f1
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001e
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002e
0x1b6862…e19c
4 touches
1 conflict
0xc13fac9b…d2d4
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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
3 conflicts on slot 0x398e1fec9f…96f13e
Audit this contract →
← previous block·next block →recent activity