← previous blocknext block →recent activity
Analyzing
Block #95,203,467
21 transactions · 18 stateful · 2026-08-12 00:23:14 UTC
Parallelism
81/100
Blocked
33%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,203,467 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w07w18w09w112w113w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd8bd73f8…27d6
0x34b655…2a6f
6 touches
3 conflicts
0x424934c8…f2f1
0x34b655…2a6f
6 touches
3 conflicts
0x020c86b9…acbf
0x34b655…2a6f
6 touches
3 conflicts
0x18e6b1c8…8a45
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0xeae24c…0be0
4 touches
1 conflict
0x23769ebc…c8ed
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x64275949…d698
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 0xd8bd73f832…ac27d6
Audit this contract →
← previous block·next block →recent activity