← previous blocknext block →recent activity
Analyzing
Block #96,665,274
7 transactions · 5 stateful · 2026-08-17 03:11:10 UTC
Parallelism
71/100
Blocked
20%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,665,274 · 7 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
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc2a783bf…25e3
0x34b655…2a6f
4 touches
1 conflict
0xea3b49a7…24d7
0x34b655…2a6f
4 touches
1 conflict
0xf145d6e1…ee85
0x34b655…2a6f
4 touches
1 conflict
0xfbe6a366…8ca1
0x34b655…2a6f
4 touches
1 conflict
0x177f744d…b7dd
0x34b655…2a6f
2 touches
0 conflicts
0x304e4e41…82fe
0x34b655…2a6f
2 touches
0 conflicts
0x8b37f931…1b3f
0x34b655…2a6f
2 touches
0 conflicts
0x8c31f591…0eab
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 0xc2a783bfdf…da25e3
Audit this contract →
← previous block·next block →recent activity