← previous blocknext block →recent activity
Analyzing
Block #98,265,374
16 transactions · 14 stateful · 2026-08-22 18:34:06 UTC
Parallelism
88/100
Blocked
21%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,265,374 · 16 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
1w04w05w113w014w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0x340143…768f
4 touches
1 conflict
0x14cc77c7…69c4
0x34b655…2a6f
2 touches
0 conflicts
0x14ee2daf…a775
0x34b655…2a6f
2 touches
0 conflicts
0x1c0be074…2a3b
0x34b655…2a6f
2 touches
0 conflicts
0x23d168fb…d916
0x34b655…2a6f
2 touches
0 conflicts
0x2830613e…c87a
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 0xbde524f475…b143bf
Audit this contract →
← previous block·next block →recent activity