← previous blocknext block →recent activity
Analyzing
Block #73,749,134
23 transactions · 19 stateful · 2026-05-10 21:00:05 UTC
Parallelism
78/100
Blocked
42%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #73,749,134 · 23 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
3w04w16w07w18w210w011w112w013w114w221w322w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6eba5e7f…4b52
0x34b655…2a6f
8 touches
6 conflicts
0x15d039e7…4bb6
0x34b655…2a6f
8 touches
6 conflicts
0xc6417de0…2191
0xc8689a…ee79
6 touches
3 conflicts
0x057de4f5…df60
0x34b655…2a6f
6 touches
3 conflicts
0xb378025c…30cf
0x34b655…2a6f
6 touches
3 conflicts
0xbb96bcbe…441d
0x34b655…2a6f
6 touches
3 conflicts
0xedb848fe…6534
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0xab3526…fa38
6 touches
3 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
6 conflicts on slot 0x6eba5e7f6a…ac4b52
Audit this contract →
← previous block·next block →recent activity