← previous blocknext block →recent activity
Analyzing
Block #98,429,875
15 transactions · 14 stateful · 2026-08-23 08:21:45 UTC
Parallelism
67/100
Blocked
43%
Avg conflicts / tx
0.73
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,429,875 · 15 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w26w29w310w111w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x187c1fa8…e0fe
0x34b655…2a6f
6 touches
3 conflicts
0xeca74ff3…a361
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x7de57974…f5ba
0x34b655…2a6f
6 touches
3 conflicts
0x565d71a1…a989
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x258fcaf5…2084
0x34b655…2a6f
6 touches
3 conflicts
0xf95f86cd…e927
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
3 conflicts on slot 0x187c1fa879…f5e0fe
Audit this contract →
← previous block·next block →recent activity