← previous blocknext block →recent activity
Analyzing
Block #98,430,307
13 transactions · 13 stateful · 2026-08-23 08:23:55 UTC
Parallelism
85/100
Blocked
23%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,430,307 · 13 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
2w05w07w19w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5934b407…e058
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x7c82b710…e9a9
0x34b655…2a6f
4 touches
1 conflict
0x8051822e…c0b8
0x34b655…2a6f
2 touches
0 conflicts
0x82f46d1e…1831
0x34b655…2a6f
2 touches
0 conflicts
0xbde4dc4a…6cb9
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 0x5934b407c2…7fe058
Audit this contract →
← previous block·next block →recent activity