← previous blocknext block →recent activity
Analyzing
Block #94,975,033
16 transactions · 15 stateful · 2026-08-11 05:13:23 UTC
Parallelism
88/100
Blocked
7%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,975,033 · 16 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
14w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3c7c65d0…0b52
0x34b655…2a6f
4 touches
1 conflict
0x13306c72…fb14
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xdc56639d…8bb9
0x34b655…2a6f
4 touches
1 conflict
0x17935a8f…a796
0x34b655…2a6f
4 touches
1 conflict
0x2697123c…8526
0x34b655…2a6f
2 touches
0 conflicts
0x35b89cd8…5092
0x34b655…2a6f
2 touches
0 conflicts
0x5770813f…1aa7
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 0x3c7c65d0e6…a00b52
Audit this contract →
← previous block·next block →recent activity