← previous blocknext block →recent activity
Analyzing
Block #98,471,067
10 transactions · 10 stateful · 2026-08-23 11:49:21 UTC
Parallelism
70/100
Blocked
30%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,471,067 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w08w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x823c5bec…e738
0x99c7a7…8bf0
4 touches
1 conflict
0xe3ae148c…7cdd
0x99c7a7…8bf0
4 touches
1 conflict
0x25d5e04e…3ef4
0x754704…b603
4 touches
1 conflict
0x64b004ab…60af
0x754704…b603
4 touches
1 conflict
0xba68e65e…c29a
0x754704…b603
4 touches
1 conflict
0x10d80fee…dbda
0x2b46c0…1669
2 touches
0 conflicts
0x40970e69…da50
0x2b46c0…1669
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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity