← previous blocknext block →recent activity
Analyzing
Block #97,913,640
16 transactions · 16 stateful · 2026-08-21 12:59:06 UTC
Parallelism
88/100
Blocked
31%
Avg conflicts / tx
0.31
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #97,913,640 · 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
1w02w13w04w05w16w07w19w010w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x286711a5…b3bf
0x34b655…2a6f
4 touches
1 conflict
0x4738f9fd…b0d4
0x34b655…2a6f
4 touches
1 conflict
0x4e365dc8…813f
0x34b655…2a6f
4 touches
1 conflict
0x54728dbe…434e
0x34b655…2a6f
4 touches
1 conflict
0x588ba065…f516
0x34b655…2a6f
4 touches
1 conflict
0x7061d006…074d
0x34b655…2a6f
4 touches
1 conflict
0x7ad16a38…ce0c
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity