← previous blocknext block →recent activity
Analyzing
Block #95,473,412
9 transactions · 9 stateful · 2026-08-12 23:14:37 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,473,412 · 9 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
2w03w14w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53f393fa…00b9
0x34b655…2a6f
4 touches
1 conflict
0x398c0e99…196a
0x34b655…2a6f
4 touches
1 conflict
0x0419260c…d009
0x34b655…2a6f
4 touches
1 conflict
0x1eced4db…6e94
0x34b655…2a6f
2 touches
0 conflicts
0x38232bf9…db72
0x34b655…2a6f
2 touches
0 conflicts
0x38befc08…20c8
0x34b655…2a6f
2 touches
0 conflicts
0x402e43c2…7ed0
0x34b655…2a6f
2 touches
0 conflicts
0x4acbdbcf…a8c6
0x34b655…2a6f
2 touches
0 conflicts
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 0x53f393fafd…2a00b9
Audit this contract →
← previous block·next block →recent activity