← previous blocknext block →recent activity
Analyzing
Block #95,424,393
18 transactions · 16 stateful · 2026-08-12 19:08:02 UTC
Parallelism
83/100
Blocked
44%
Avg conflicts / tx
0.67
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,424,393 · 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
2w03w04w16w28w09w011w112w113w214w215w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4e169881…8c80
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0xeae24c…0be0
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x160f117d…8e90
0x065c9d…c394
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0xb33ff823…1188
0x065c9d…c394
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 0x4e16988114…ee8c80
Audit this contract →
← previous block·next block →recent activity