← previous blocknext block →recent activity
Analyzing
Block #98,064,935
18 transactions · 18 stateful · 2026-08-22 01:44:57 UTC
Parallelism
83/100
Blocked
44%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,064,935 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w06w18w09w111w212w014w115w116w217w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3f428985…58dc
0x34b655…2a6f
4 touches
1 conflict
0xb575cf74…fbd5
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe0f7dede…bc98
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2593
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 0x3f4289859a…e258dc
Audit this contract →
← previous block·next block →recent activity