← previous blocknext block →recent activity
Analyzing
Block #73,869,517
8 transactions · 6 stateful · 2026-05-11 10:26:38 UTC
Parallelism
75/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,869,517 · 8 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
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5584844…a5e5
0x34b655…2a6f
4 touches
1 conflict
0x15d039e7…4bb6
0x34b655…2a6f
4 touches
1 conflict
0xa3ff1ab2…8ae3
0x34b655…2a6f
4 touches
1 conflict
0xb8228d38…3953
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x7f81fb82…633e
0x065c9d…c394
2 touches
0 conflicts
0xb159af88…a9e7
0x065c9d…c394
2 touches
0 conflicts
0xb2bd1fd4…94bd
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 0xe558484421…83a5e5
Audit this contract →
← previous block·next block →recent activity