← previous blocknext block →recent activity
Analyzing
Block #98,428,589
17 transactions · 16 stateful · 2026-08-23 08:15:17 UTC
Parallelism
76/100
Blocked
50%
Avg conflicts / tx
0.82
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,428,589 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w28w39w010w112w013w114w215w316w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xbb3f3c…e046
8 touches
6 conflicts
0xa6c4cb16…517c
0xd32edf…ff58
7 touches
6 conflicts
0xd6bd849a…5597
0x2a68ba…90c5
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0xf12a8246…e00f
0xa6afd3…d132
4 touches
1 conflict
0xb480ad11…3840
0xa6afd3…d132
3 touches
1 conflict
0x00000000…0003
0x63e48b…53f2
2 touches
0 conflicts
0x00000000…0004
0x63e48b…53f2
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: 0xbb3f3cb7…74e046
6 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity