← previous blocknext block →recent activity
Analyzing
Block #73,668,636
11 transactions · 8 stateful · 2026-05-10 11:56:51 UTC
Parallelism
73/100
Blocked
38%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,668,636 · 11 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
1w03w14w08w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0ac31945…2c72
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x5c409aa9…0804
0x065c9d…c394
4 touches
1 conflict
0x3e733ae4…4598
0x34b655…2a6f
4 touches
1 conflict
0x4de8ad37…12f2
0x065c9d…c394
3 touches
1 conflict
0xd6a3dca1…41de
0x065c9d…c394
2 touches
0 conflicts
0xf5e1dec0…fd45
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity