← previous blocknext block →recent activity
Analyzing
Block #98,273,359
35 transactions · 27 stateful · 2026-08-22 19:14:16 UTC
Parallelism
86/100
Blocked
44%
Avg conflicts / tx
0.49
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,273,359 · 35 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w05w114w015w116w217w018w119w121w022w124w325w026w129w431w232w334w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x801a6e57…d85c
0x34b655…2a6f
6 touches
3 conflicts
0x8c49c85c…ee96
0x34b655…2a6f
6 touches
3 conflicts
0x41755291…977f
0x065c9d…c394
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…0007
0x340143…768f
4 touches
1 conflict
0x085df2c1…305a
0x34b655…2a6f
4 touches
1 conflict
0x2999ebda…ce6c
0x34b655…2a6f
4 touches
1 conflict
0x2b6e2a61…3dae
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 0x801a6e5726…c1d85c
Audit this contract →
← previous block·next block →recent activity