← previous blocknext block →recent activity
Analyzing
Block #98,435,204
25 transactions · 20 stateful · 2026-08-23 08:48:33 UTC
Parallelism
88/100
Blocked
30%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,435,204 · 25 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
2w03w14w26w08w09w112w214w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5ddc4a77…765e
0x34b655…2a6f
6 touches
3 conflicts
0x7de57974…f5ba
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xdb1e37cb…90c9
0x34b655…2a6f
4 touches
1 conflict
0xedd788b4…15ce
0x34b655…2a6f
4 touches
1 conflict
0xaf30a686…dc84
0x34b655…2a6f
4 touches
1 conflict
0xfe2bac2b…2cec
0x065c9d…c394
4 touches
1 conflict
0x482471ad…122f
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 0x5ddc4a7765…4b765e
Audit this contract →
← previous block·next block →recent activity