← previous blocknext block →recent activity
Analyzing
Block #73,683,344
18 transactions · 15 stateful · 2026-05-10 13:36:15 UTC
Parallelism
72/100
Blocked
53%
Avg conflicts / tx
0.89
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #73,683,344 · 18 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
3w04w15w26w07w18w29w310w415w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
10 touches
10 conflicts
0x8a35acfb…d1ab
0x8d66a4…3095
8 touches
6 conflicts
0x3e733ae4…4598
0x34b655…2a6f
6 touches
3 conflicts
0xe96c91d2…32ff
0x8d66a4…3095
6 touches
3 conflicts
0x00000000…0002
0xab3526…fa38
6 touches
3 conflicts
0x9be2b99a…a959
0x34b655…2a6f
4 touches
1 conflict
0xa91c899f…6ee3
0x34b655…2a6f
4 touches
1 conflict
0xcfdbe862…6b0e
0x34b655…2a6f
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
10 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity