← previous blocknext block →recent activity
Analyzing
Block #74,304,770
8 transactions · 6 stateful · 2026-05-13 10:45:05 UTC
Parallelism
75/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,304,770 · 8 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
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1b5d2e60…99b5
0x34b655…2a6f
4 touches
1 conflict
0xa92c8763…6d7f
0x34b655…2a6f
4 touches
1 conflict
0xfa2527aa…9dd5
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x6a2aae37…1240
0x065c9d…c394
2 touches
0 conflicts
0xacb2faea…fd92
0x065c9d…c394
2 touches
0 conflicts
0xc32dcaed…905f
0x065c9d…c394
2 touches
0 conflicts
0xde59d190…0ec1
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 0x1b5d2e607a…9999b5
Audit this contract →
← previous block·next block →recent activity