← previous blocknext block →recent activity
Analyzing
Block #95,288,536
18 transactions · 16 stateful · 2026-08-12 07:40:07 UTC
Parallelism
67/100
Blocked
44%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,288,536 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w59w010w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x52c63247…ce02
0x0a3323…0a3c
12 touches
15 conflicts
0x446f2734…8b54
0x0a3323…0a3c
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x317fc387…8bf2
0x0a3323…0a3c
4 touches
1 conflict
0xff3addfc…633e
0x6f4756…dd5b
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0xdb3f6210…2c83
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: 0x0a332311…6e0a3c
15 conflicts on slot 0x52c63247e1…bace02
Audit this contract →
← previous block·next block →recent activity