← previous blocknext block →recent activity
Analyzing
Block #74,240,309
7 transactions · 6 stateful · 2026-05-13 03:36:24 UTC
Parallelism
71/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,240,309 · 7 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
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc9b39579…408c
0x34b655…2a6f
4 touches
1 conflict
0x2877f440…c2c8
0x34b655…2a6f
4 touches
1 conflict
0x768cffcd…2648
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x3d2a39e9…f078
0x065c9d…c394
2 touches
0 conflicts
0x5b5eb6a6…e3b0
0x065c9d…c394
2 touches
0 conflicts
0x6e8492c0…127f
0x065c9d…c394
2 touches
0 conflicts
0x9142e73c…1e36
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 0xc9b3957972…08408c
Audit this contract →
← previous block·next block →recent activity