← previous blocknext block →recent activity
Analyzing
Block #94,963,258
13 transactions · 13 stateful · 2026-08-11 04:14:11 UTC
Parallelism
85/100
Blocked
23%
Avg conflicts / tx
0.31
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,963,258 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w16w07w19w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2b5101ac…090b
0x34b655…2a6f
4 touches
1 conflict
0xc4328d82…54c2
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x595233b5…c4aa
0x754704…b603
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x5aed1bd2…7afa
0x34b655…2a6f
2 touches
0 conflicts
0x5d782da3…0d95
0x34b655…2a6f
2 touches
0 conflicts
0x6cd5cae5…1031
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 0x2b5101acd1…7c090b
Audit this contract →
← previous block·next block →recent activity