← previous blocknext block →recent activity
Analyzing
Block #73,968,383
7 transactions · 6 stateful · 2026-05-11 21:24:46 UTC
Parallelism
57/100
Blocked
33%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,968,383 · 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
0xee230b20…5a0f
0x34b655…2a6f
4 touches
1 conflict
0xf853eb8e…4027
0x34b655…2a6f
4 touches
1 conflict
0xac8e97a0…8426
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x310b1de7…4bb7
0x065c9d…c394
2 touches
0 conflicts
0x3e4d3d97…e562
0x065c9d…c394
2 touches
0 conflicts
0x74468fa3…92f9
0x065c9d…c394
2 touches
0 conflicts
0x92474f11…3fca
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 0xee230b202a…c05a0f
Audit this contract →
← previous block·next block →recent activity