← previous blocknext block →recent activity
Analyzing
Block #98,430,748
10 transactions · 9 stateful · 2026-08-23 08:26:08 UTC
Parallelism
70/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,430,748 · 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
5w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7c82b710…e9a9
0x34b655…2a6f
4 touches
1 conflict
0x9e1c65d0…77a3
0x34b655…2a6f
4 touches
1 conflict
0xb6c92107…e6d7
0x34b655…2a6f
4 touches
1 conflict
0xbde4dc4a…6cb9
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xe90322ad…33d1
0x34b655…2a6f
4 touches
1 conflict
0x04702926…9854
0x059114…ac3b
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 0x7c82b710c8…aae9a9
Audit this contract →
← previous block·next block →recent activity