← previous blocknext block →recent activity
Analyzing
Block #98,416,298
13 transactions · 13 stateful · 2026-08-23 07:13:26 UTC
Parallelism
85/100
Blocked
31%
Avg conflicts / tx
0.46
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,416,298 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w06w07w18w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbda105bc…24a8
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0x4de0b2a2…784f
0xc8689a…ee79
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0xa450ad4b…c2d5
0xa6afd3…d132
4 touches
1 conflict
0x6c19e76e…13e4
0xa6afd3…d132
4 touches
1 conflict
0x62910921…3016
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
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
1 conflict on slot 0xbda105bc2e…f924a8
Audit this contract →
← previous block·next block →recent activity