← previous blocknext block →recent activity
Analyzing
Block #73,983,954
14 transactions · 9 stateful · 2026-05-11 23:09:20 UTC
Parallelism
86/100
Blocked
22%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,983,954 · 14 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
1w05w06w111w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x003a4349…8361
0x065c9d…c394
2 touches
0 conflicts
0xa67bb957…4fdf
0x065c9d…c394
2 touches
0 conflicts
0xa6bc0981…ac2b
0x065c9d…c394
2 touches
0 conflicts
0xd65f4833…41b3
0x065c9d…c394
2 touches
0 conflicts
0xf537eaa0…73c8
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