← previous blocknext block →recent activity
Analyzing
Block #73,960,311
9 transactions · 8 stateful · 2026-05-11 20:31:04 UTC
Parallelism
78/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,960,311 · 9 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
2w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb91a6f59…722c
0x34b655…2a6f
4 touches
1 conflict
0xc4ac64a3…ebbc
0x34b655…2a6f
4 touches
1 conflict
0xf6476f21…3580
0x34b655…2a6f
4 touches
1 conflict
0x0cca8372…aba3
0x065c9d…c394
2 touches
0 conflicts
0x3d6947b4…0ad5
0x065c9d…c394
2 touches
0 conflicts
0x4028aeae…d458
0x065c9d…c394
2 touches
0 conflicts
0xc35c017f…15df
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
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 0xb91a6f59b9…c8722c
Audit this contract →
← previous block·next block →recent activity