← previous blocknext block →recent activity
Analyzing
Block #95,798,516
14 transactions · 12 stateful · 2026-08-14 02:30:49 UTC
Parallelism
79/100
Blocked
33%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,798,516 · 14 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
2w04w06w09w110w211w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53bda555…3810
0x34b655…2a6f
6 touches
3 conflicts
0x44a2c3ff…0abc
0x34b655…2a6f
6 touches
3 conflicts
0x78860c4f…cade
0x34b655…2a6f
4 touches
1 conflict
0x85e82d49…7e79
0x34b655…2a6f
4 touches
1 conflict
0xe21234e7…bded
0x34b655…2a6f
4 touches
1 conflict
0xe9452241…95a3
0x34b655…2a6f
4 touches
1 conflict
0x1a5d321d…a474
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
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
3 conflicts on slot 0x53bda5555c…603810
Audit this contract →
← previous block·next block →recent activity