← previous blocknext block →recent activity
Analyzing
Block #74,555,673
22 transactions · 11 stateful · 2026-05-14 14:39:26 UTC
Parallelism
91/100
Blocked
36%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,555,673 · 22 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
1w04w07w110w111w012w117w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb533aa27…7f13
0x34b655…2a6f
4 touches
1 conflict
0x01e7b865…6e6d
0x188d58…ea8e
4 touches
1 conflict
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x05e81f73…871f
0xd32edf…ff58
3 touches
1 conflict
0x335a161d…fe7f
0x000000…012a
2 touches
0 conflicts
0xeda2edc3…91d8
0x000000…012a
2 touches
0 conflicts
0x01e7b865…6e6f
0x188d58…ea8e
2 touches
0 conflicts
0x2f77f0f6…4a92
0x188d58…ea8e
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 0xb533aa27ea…df7f13
Audit this contract →
← previous block·next block →recent activity