← previous blocknext block →recent activity
Analyzing
Block #98,984,129
14 transactions · 11 stateful · 2026-08-25 07:26:47 UTC
Parallelism
71/100
Blocked
36%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,984,129 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w07w08w19w110w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x127b1e72…053c
0x34b655…2a6f
8 touches
6 conflicts
0xe796f8b7…ad55
0x34b655…2a6f
8 touches
6 conflicts
0xdb11940a…519b
0x34b655…2a6f
6 touches
3 conflicts
0xd8b569b6…2b51
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f1
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 0x127b1e72e9…ed053c
Audit this contract →
← previous block·next block →recent activity