← previous blocknext block →recent activity
Analyzing
Block #95,088,643
16 transactions · 14 stateful · 2026-08-11 14:45:40 UTC
Parallelism
88/100
Blocked
21%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,088,643 · 16 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
7w08w010w011w112w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf6deafb5…5c25
0x34b655…2a6f
4 touches
1 conflict
0x5311f864…0984
0x754704…b603
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xf40fa0f3…13cf
0xe52b14…7230
3 touches
1 conflict
0x6ede85f4…0b8b
0x928dc8…8207
2 touches
0 conflicts
0x7751cbb9…c69a
0x928dc8…8207
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 0xf6deafb553…9e5c25
Audit this contract →
← previous block·next block →recent activity