← previous blocknext block →recent activity
Analyzing
Block #97,731,895
18 transactions · 18 stateful · 2026-08-20 21:34:39 UTC
Parallelism
67/100
Blocked
44%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,731,895 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w05w16w27w39w410w412w515w016w217w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3df3de0d…cd8b
0x34b655…2a6f
6 touches
3 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0xdaa0495a…3047
0x34b655…2a6f
6 touches
3 conflicts
0x0bc43347…93d4
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x43357924…e89d
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x68c23664…74c4
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
3 conflicts on slot 0x3df3de0dae…bccd8b
Audit this contract →
← previous block·next block →recent activity