← previous blocknext block →recent activity
Analyzing
Block #95,379,294
25 transactions · 23 stateful · 2026-08-12 15:19:53 UTC
Parallelism
88/100
Blocked
39%
Avg conflicts / tx
0.48
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,379,294 · 25 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
2w03w14w05w06w17w110w011w012w114w117w118w119w220w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe8eae8a3…bacc
0x34b655…2a6f
6 touches
3 conflicts
0xb33ff823…1188
0x065c9d…c394
4 touches
1 conflict
0x11258774…9892
0x2a68ba…90c5
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x0bd95eb4…e562
0x34b655…2a6f
4 touches
1 conflict
0x3439dfbc…0d03
0x34b655…2a6f
4 touches
1 conflict
0x6e6a8155…9636
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
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
3 conflicts on slot 0xe8eae8a323…64bacc
Audit this contract →
← previous block·next block →recent activity