← previous blocknext block →recent activity
Analyzing
Block #98,751,559
16 transactions · 14 stateful · 2026-08-24 11:56:23 UTC
Parallelism
88/100
Blocked
21%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,751,559 · 16 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
1w02w14w19w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0008
0x8964d7…10f8
4 touches
1 conflict
0x2dc1eae9…3477
0x8964d7…10f8
4 touches
1 conflict
0x2dc1eae9…3478
0x8964d7…10f8
4 touches
1 conflict
0x2dc1eae9…347b
0x8964d7…10f8
4 touches
1 conflict
0x2dc1eae9…347c
0x8964d7…10f8
4 touches
1 conflict
0x2dc1eae9…347e
0x8964d7…10f8
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
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: 0x8964d7c9…5b10f8
1 conflict on slot 0x0000000000…000008
Audit this contract →
← previous block·next block →recent activity