← previous blocknext block →recent activity
Analyzing
Block #98,670,997
16 transactions · 14 stateful · 2026-08-24 05:06:28 UTC
Parallelism
81/100
Blocked
36%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,670,997 · 16 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
5w06w18w09w110w111w214w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c20d376…0819
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b78
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x35cb8e5d…d583
0xd32edf…ff58
3 touches
1 conflict
0xef05d32a…8897
0x34b655…2a6f
3 touches
1 conflict
0x7c403af1…31b1
0x3bd359…433a
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 0x4c20d37631…040819
Audit this contract →
← previous block·next block →recent activity