← previous blocknext block →recent activity
Analyzing
Block #96,281,702
16 transactions · 13 stateful · 2026-08-15 19:01:40 UTC
Parallelism
81/100
Blocked
23%
Avg conflicts / tx
0.19
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,281,702 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w07w19w213w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5b0edc1d…65d6
0x34b655…2a6f
4 touches
1 conflict
0x9a3463f0…0b73
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0xd3a600a5…8c65
0x34b655…2a6f
4 touches
1 conflict
0xeca3f7cd…57b6
0x34b655…2a6f
4 touches
1 conflict
0xeca3f7cd…57b7
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
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
1 conflict on slot 0x5b0edc1db7…3765d6
Audit this contract →
← previous block·next block →recent activity