← previous blocknext block →recent activity
Analyzing
Block #98,499,753
25 transactions · 24 stateful · 2026-08-23 14:13:52 UTC
Parallelism
76/100
Blocked
33%
Avg conflicts / tx
0.68
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,499,753 · 25 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
1w02w14w010w011w113w215w316w018w122w323w424w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5f1
0x34b655…2a6f
8 touches
6 conflicts
0x7aad02c6…b979
0x34b655…2a6f
8 touches
6 conflicts
0xb4b350eb…8c96
0x34b655…2a6f
8 touches
6 conflicts
0x398e1fec…f13e
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x58b3e198…25a7
0x34b655…2a6f
4 touches
1 conflict
0x83042142…c1b6
0x34b655…2a6f
4 touches
1 conflict
0x91b1789a…cb1b
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
6 conflicts on slot 0xe5bb3628b5…71e5f1
Audit this contract →
← previous block·next block →recent activity