← previous blocknext block →recent activity
Analyzing
Block #74,249,885
7 transactions · 7 stateful · 2026-05-13 04:40:06 UTC
Parallelism
57/100
Blocked
29%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #74,249,885 · 7 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
2w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x768cffcd…2648
0x34b655…2a6f
6 touches
3 conflicts
0xa8ddf3d3…ece4
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xfe20cb8f…f03d
0x34b655…2a6f
4 touches
1 conflict
0x1eb0fab5…3517
0x34b655…2a6f
4 touches
1 conflict
0x610af092…8ad3
0x34b655…2a6f
4 touches
1 conflict
0xcf3283ba…c9fa
0x065c9d…c394
2 touches
0 conflicts
0xf4659af6…0446
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
3 conflicts on slot 0x768cffcdb0…d12648
Audit this contract →
← previous block·next block →recent activity