← previous blocknext block →recent activity
Analyzing
Block #95,472,499
28 transactions · 28 stateful · 2026-08-12 23:10:01 UTC
Parallelism
89/100
Blocked
7%
Avg conflicts / tx
0.11
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,472,499 · 28 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
2w04w125w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb1c67a7d…b9b1
0x34b655…2a6f
4 touches
1 conflict
0x31b39922…1e66
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x34745c12…4e06
0x34b655…2a6f
4 touches
1 conflict
0x367b69ad…33d8
0x34b655…2a6f
4 touches
1 conflict
0x367b69ad…33d9
0x34b655…2a6f
4 touches
1 conflict
0x3a5e95ba…806a
0x34b655…2a6f
4 touches
1 conflict
0x4cb450ac…4047
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 0xb1c67a7d65…cdb9b1
Audit this contract →
← previous block·next block →recent activity