← previous blocknext block →recent activity
Analyzing
Block #95,204,465
21 transactions · 21 stateful · 2026-08-12 00:28:16 UTC
Parallelism
76/100
Blocked
38%
Avg conflicts / tx
0.81
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,204,465 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w05w18w09w110w211w312w413w219w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe1902c61…65ad
0xe52b14…7230
10 touches
10 conflicts
0xe1902c61…65af
0xe52b14…7230
10 touches
10 conflicts
0xf79df061…e005
0xe52b14…7230
10 touches
10 conflicts
0xa6e37efb…afc0
0xe52b14…7230
10 touches
10 conflicts
0xa6e37efb…afc2
0xe52b14…7230
10 touches
10 conflicts
0xadb6be75…98bd
0xe52b14…7230
8 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x96dd83e6…a507
0x34b655…2a6f
6 touches
3 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: 0xe52b1424…bb7230
10 conflicts on slot 0xe1902c61a4…8e65ad
Audit this contract →
← previous block·next block →recent activity