← previous blocknext block →recent activity
Analyzing
Block #95,808,178
14 transactions · 9 stateful · 2026-08-14 03:19:25 UTC
Parallelism
71/100
Blocked
44%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,808,178 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w26w37w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2c602697…299d
0x34b655…2a6f
8 touches
6 conflicts
0x6581d38b…076f
0x34b655…2a6f
8 touches
6 conflicts
0xb9b077a8…e029
0x34b655…2a6f
4 touches
1 conflict
0xd79c9727…1233
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xf6deafb5…5c25
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x002fed35…79fa
0x2a68ba…90c5
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
6 conflicts on slot 0x2c60269724…f6299d
Audit this contract →
← previous block·next block →recent activity