← previous blocknext block →recent activity
Analyzing
Block #97,817,438
13 transactions · 13 stateful · 2026-08-21 04:46:17 UTC
Parallelism
85/100
Blocked
23%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #97,817,438 · 13 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
2w03w04w16w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4de40a98…ee65
0x34b655…2a6f
4 touches
1 conflict
0xbff09f1a…d50a
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x4ce27151…5a74
0x34b655…2a6f
4 touches
1 conflict
0xe75ce681…ba60
0x188d58…ea8e
2 touches
0 conflicts
0xd6bd849a…5597
0x2a68ba…90c5
2 touches
0 conflicts
0x2a85a97d…1444
0x34b655…2a6f
2 touches
0 conflicts
0x7de57974…f5ba
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 0x4de40a988e…f8ee65
Audit this contract →
← previous block·next block →recent activity