← previous blocknext block →recent activity
Analyzing
Block #74,034,693
8 transactions · 7 stateful · 2026-05-12 04:48:28 UTC
Parallelism
63/100
Blocked
43%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #74,034,693 · 8 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd49762c9…1359
0x34b655…2a6f
4 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x266994c9…a47a
0x065c9d…c394
2 touches
0 conflicts
0x55801efc…5ad3
0x065c9d…c394
2 touches
0 conflicts
0x5937dc41…f876
0x065c9d…c394
2 touches
0 conflicts
0xf2041b61…78be
0x065c9d…c394
2 touches
0 conflicts
0xf42abb76…310d
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 0xd49762c96f…3b1359
Audit this contract →
← previous block·next block →recent activity