← previous blocknext block →recent activity
Analyzing
Block #98,569,455
30 transactions · 25 stateful · 2026-08-23 20:17:38 UTC
Parallelism
77/100
Blocked
44%
Avg conflicts / tx
0.63
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #98,569,455 · 30 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
7w08w09w110w011w117w118w219w320w421w522w223w625w226w027w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5f1
0x34b655…2a6f
8 touches
6 conflicts
0x5784baac…ac7e
0x34b655…2a6f
8 touches
6 conflicts
0xf3981be5…2c47
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xa9c3560d…8f54
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…002e
0x1b6862…e19c
4 touches
1 conflict
0x75e73565…45fa
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
6 conflicts on slot 0xe5bb3628b5…71e5f1
Audit this contract →
← previous block·next block →recent activity