← previous blocknext block →recent activity
Analyzing
Block #74,698,289
13 transactions · 11 stateful · 2026-05-15 06:32:44 UTC
Parallelism
85/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,698,289 · 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
11w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9dc9fa5f…7f23
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x8a85cf3d…2868
0x34b655…2a6f
4 touches
1 conflict
0x01e7b865…6e70
0x188d58…ea8e
2 touches
0 conflicts
0x8be41ef9…2930
0x188d58…ea8e
2 touches
0 conflicts
0xc07f9857…7ab4
0x188d58…ea8e
2 touches
0 conflicts
0xd01e487f…2223
0x188d58…ea8e
2 touches
0 conflicts
0xd01e487f…2224
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 0x9dc9fa5fdc…257f23
Audit this contract →
← previous block·next block →recent activity