← previous blocknext block →recent activity
Analyzing
Block #98,472,593
14 transactions · 14 stateful · 2026-08-23 11:57:01 UTC
Parallelism
71/100
Blocked
36%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,472,593 · 14 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
2w04w16w17w212w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1c389468…6b0e
0x34b655…2a6f
6 touches
3 conflicts
0x84d7a5ea…06dc
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x3d63a10e…72b4
0x34b655…2a6f
4 touches
1 conflict
0x2734e00b…9b4f
0x3bd359…433a
2 touches
0 conflicts
0xea9082f4…04a2
0x3bd359…433a
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
3 conflicts on slot 0x1c38946843…a16b0e
Audit this contract →
← previous block·next block →recent activity