← previous blocknext block →recent activity
Analyzing
Block #98,149,246
23 transactions · 20 stateful · 2026-08-22 08:49:53 UTC
Parallelism
91/100
Blocked
10%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,149,246 · 23 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
1w016w017w020w122w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb13b96bd…a3cb
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0x340143…768f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0xd6bd849a…5597
0x2a68ba…90c5
2 touches
0 conflicts
0xb05cd4f5…73d0
0x2b46c0…1669
2 touches
0 conflicts
0xeba56708…8cd7
0x2b46c0…1669
2 touches
0 conflicts
0x1220566c…6e14
0x34b655…2a6f
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 0xb13b96bd5b…77a3cb
Audit this contract →
← previous block·next block →recent activity