← previous blocknext block →recent activity
Analyzing
Block #74,246,471
16 transactions · 11 stateful · 2026-05-13 04:17:25 UTC
Parallelism
63/100
Blocked
55%
Avg conflicts / tx
0.56
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #74,246,471 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w06w17w213w314w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x5de96bd3…c60c
0x34b655…2a6f
6 touches
3 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0xb7307664…f7b2
0x065c9d…c394
4 touches
1 conflict
0xc24e3828…bf17
0x065c9d…c394
4 touches
1 conflict
0xcf3283ba…c9fa
0x065c9d…c394
4 touches
1 conflict
0xf154eea7…323c
0x065c9d…c394
4 touches
1 conflict
0xf823e97f…2ee6
0x065c9d…c394
4 touches
1 conflict
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity