← previous blocknext block →recent activity
Analyzing
Block #96,354,045
10 transactions · 7 stateful · 2026-08-16 01:05:31 UTC
Parallelism
80/100
Blocked
14%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,354,045 · 10 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
6w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeca3f7cd…57b7
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x2fdfa032…139c
0x34b655…2a6f
4 touches
1 conflict
0x5b0edc1d…65d6
0x34b655…2a6f
4 touches
1 conflict
0x92d4e9d1…b273
0x34b655…2a6f
4 touches
1 conflict
0xda37c150…d25c
0x34b655…2a6f
4 touches
1 conflict
0xeca3f7cd…57b6
0x34b655…2a6f
4 touches
1 conflict
0x28f41311…2299
0x34b655…2a6f
3 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 0xeca3f7cd6e…1257b7
Audit this contract →
← previous block·next block →recent activity