← previous blocknext block →recent activity
Analyzing
Block #95,540,631
18 transactions · 18 stateful · 2026-08-13 04:52:43 UTC
Parallelism
83/100
Blocked
22%
Avg conflicts / tx
0.28
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,540,631 · 18 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
2w03w17w28w09w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ccc60f5…00f3
0x34b655…2a6f
4 touches
1 conflict
0x9d80f2dd…9e29
0x34b655…2a6f
4 touches
1 conflict
0xb7436916…28a4
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x00e21a9f…3583
0x34b655…2a6f
4 touches
1 conflict
0xb33ff823…1188
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x349f436e…80e6
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 0x9ccc60f58c…5c00f3
Audit this contract →
← previous block·next block →recent activity