← previous blocknext block →recent activity
Analyzing
Block #96,640,376
18 transactions · 12 stateful · 2026-08-17 01:05:56 UTC
Parallelism
89/100
Blocked
25%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,640,376 · 18 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
1w07w112w013w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6bdb9869…7558
0x34b655…2a6f
4 touches
1 conflict
0x11258774…9892
0x2a68ba…90c5
4 touches
1 conflict
0x5e7e0120…7bb9
0x34b655…2a6f
4 touches
1 conflict
0xa35509fa…5cb3
0x34b655…2a6f
4 touches
1 conflict
0x745952b2…d90c
0x34b655…2a6f
4 touches
1 conflict
0x9e089d27…ab74
0x34b655…2a6f
4 touches
1 conflict
0x3b78b87d…b213
0x065c9d…c394
3 touches
1 conflict
0xf6cc7de8…0b4a
0x3bd359…433a
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 0x6bdb9869c7…427558
Audit this contract →
← previous block·next block →recent activity