← previous blocknext block →recent activity
Analyzing
Block #74,368,943
25 transactions · 13 stateful · 2026-05-13 17:51:52 UTC
Parallelism
80/100
Blocked
54%
Avg conflicts / tx
0.48
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #74,368,943 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w112w015w116w121w122w223w324w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x62d080e9…4a7c
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x7170c140…36bc
0x34b655…2a6f
6 touches
3 conflicts
0x1c348b58…836a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0xd7b68482…3234
0x065c9d…c394
4 touches
1 conflict
0x050a4348…907a
0x34b655…2a6f
4 touches
1 conflict
0x41755291…977f
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
6 conflicts on slot 0x62d080e928…5a4a7c
Audit this contract →
← previous block·next block →recent activity