← previous blocknext block →recent activity
Analyzing
Block #95,298,829
10 transactions · 8 stateful · 2026-08-12 08:32:11 UTC
Parallelism
60/100
Blocked
38%
Avg conflicts / tx
0.3
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,298,829 · 10 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
2w03w14w26w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x468d132a…d7b8
0x34b655…2a6f
4 touches
1 conflict
0x5d041208…74ae
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0x201d7cf1…f7f2
0x34b655…2a6f
2 touches
0 conflicts
0x28003a84…1751
0x34b655…2a6f
2 touches
0 conflicts
0x281f1511…22cb
0x34b655…2a6f
2 touches
0 conflicts
0x71059f3f…1e22
0x34b655…2a6f
2 touches
0 conflicts
0x71756e9d…cf15
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 0x468d132ac7…d0d7b8
Audit this contract →
← previous block·next block →recent activity