← previous blocknext block →recent activity
Analyzing
Block #94,970,021
14 transactions · 13 stateful · 2026-08-11 04:48:11 UTC
Parallelism
57/100
Blocked
38%
Avg conflicts / tx
0.79
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #94,970,021 · 14 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w211w312w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xae28870c…072f
0x34b655…2a6f
8 touches
6 conflicts
0xc0b9bd73…7f1c
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x177e0765…42b0
0x34b655…2a6f
6 touches
3 conflicts
0x2fdfa032…139c
0x34b655…2a6f
4 touches
1 conflict
0xe011112f…e484
0x34b655…2a6f
4 touches
1 conflict
0x65f90aa4…c97f
0x34b655…2a6f
4 touches
1 conflict
0x72ed31c7…de4d
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
6 conflicts on slot 0xae28870c63…13072f
Audit this contract →
← previous block·next block →recent activity