← previous blocknext block →recent activity
Analyzing
Block #98,661,832
15 transactions · 15 stateful · 2026-08-24 04:18:46 UTC
Parallelism
73/100
Blocked
27%
Avg conflicts / tx
0.27
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,661,832 · 15 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
1w02w13w26w39w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf98db8ee…a56d
0x34b655…2a6f
4 touches
1 conflict
0x00f19757…9252
0x34b655…2a6f
4 touches
1 conflict
0x287cc2c3…cc3e
0x34b655…2a6f
4 touches
1 conflict
0x503e76d4…d4eb
0x34b655…2a6f
4 touches
1 conflict
0x5ee07d61…5328
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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
1 conflict on slot 0xf98db8ee72…13a56d
Audit this contract →
← previous block·next block →recent activity