← previous blocknext block →recent activity
Analyzing
Block #73,212,113
12 transactions · 7 stateful · 2026-05-08 09:15:51 UTC
Parallelism
83/100
Blocked
43%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,212,113 · 12 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
1w02w13w010w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53c41998…7d52
0x34b655…2a6f
4 touches
1 conflict
0x7f430e47…4cbd
0x8d66a4…3095
4 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x8a35acfb…d1ad
0x8d66a4…3095
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x51087f5a…61f7
0x34b655…2a6f
2 touches
0 conflicts
0x5150abbe…43c3
0x34b655…2a6f
2 touches
0 conflicts
0x5ae0591f…3054
0x34b655…2a6f
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 0x53c41998b8…357d52
Audit this contract →
← previous block·next block →recent activity