← previous blocknext block →recent activity
Analyzing
Block #95,205,777
12 transactions · 12 stateful · 2026-08-12 00:34:52 UTC
Parallelism
83/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,205,777 · 12 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
2w04w06w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3fa807b1…33e4
0x34b655…2a6f
4 touches
1 conflict
0x31b39922…1e66
0x34b655…2a6f
4 touches
1 conflict
0xd3537c0b…fb4b
0x34b655…2a6f
4 touches
1 conflict
0x86294348…d50c
0x40c49f…2af0
3 touches
1 conflict
0x85b91f26…d3e4
0x34b655…2a6f
2 touches
0 conflicts
0x41a75cd5…4527
0xea1b8e…c5ec
2 touches
0 conflicts
0x6eff5416…605d
0xea1b8e…c5ec
2 touches
0 conflicts
0x743f204d…b9da
0xea1b8e…c5ec
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: Perpl
1 conflict on slot 0x3fa807b19d…ad33e4
Audit this contract →
← previous block·next block →recent activity