← previous blocknext block →recent activity
Analyzing
Block #98,413,860
28 transactions · 25 stateful · 2026-08-23 07:01:10 UTC
Parallelism
79/100
Blocked
44%
Avg conflicts / tx
0.75
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,413,860 · 28 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w07w19w010w111w012w114w215w317w118w419w024w125w126w227w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x386e26c3…fa30
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x15b3ea9f…ef46
0x34b655…2a6f
6 touches
3 conflicts
0x2b78ba10…9ce5
0x34b655…2a6f
6 touches
3 conflicts
0x15698ac9…2a46
0x34b655…2a6f
6 touches
3 conflicts
0xbc112522…45d0
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
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 0x386e26c3f8…64fa30
Audit this contract →
← previous block·next block →recent activity