← previous blocknext block →recent activity
Analyzing
Block #96,132,412
14 transactions · 11 stateful · 2026-08-15 06:30:47 UTC
Parallelism
79/100
Blocked
36%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,132,412 · 14 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
2w04w15w26w08w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x446f2734…8b54
0x0a3323…0a3c
6 touches
3 conflicts
0xf5fefc40…8baf
0x34b655…2a6f
6 touches
3 conflicts
0x52c63247…ce02
0x0a3323…0a3c
6 touches
3 conflicts
0xff3addfc…633e
0x6f4756…dd5b
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x35c29640…8779
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
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: 0x0a332311…6e0a3c
3 conflicts on slot 0x446f273453…878b54
Audit this contract →
← previous block·next block →recent activity