← previous blocknext block →recent activity
Analyzing
Block #74,727,076
10 transactions · 8 stateful · 2026-05-15 09:44:54 UTC
Parallelism
80/100
Blocked
25%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,727,076 · 10 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
1w06w18w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x801a6e57…d85c
0x34b655…2a6f
4 touches
1 conflict
0xb138d087…4689
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xfc6205fa…4d80
0x34b655…2a6f
4 touches
1 conflict
0x0f1697ac…d923
0xd32edf…ff58
3 touches
1 conflict
0xab38e850…e93a
0x065c9d…c394
2 touches
0 conflicts
0xb088fac3…b7a7
0x065c9d…c394
2 touches
0 conflicts
0xfe2bac2b…2cec
0x065c9d…c394
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 0x801a6e5726…c1d85c
Audit this contract →
← previous block·next block →recent activity