← previous blocknext block →recent activity
Analyzing
Block #73,642,883
10 transactions · 9 stateful · 2026-05-10 09:03:14 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,642,883 · 10 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
2w03w18w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf853eb8e…401e
0x34b655…2a6f
4 touches
1 conflict
0xb96e29a5…0419
0x34b655…2a6f
4 touches
1 conflict
0xc3aacf13…6b3d
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x334b8107…8f73
0x34b655…2a6f
2 touches
0 conflicts
0x4089d428…b018
0x34b655…2a6f
2 touches
0 conflicts
0x4ee0b65a…6d40
0x34b655…2a6f
2 touches
0 conflicts
0x73113592…0f2d
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 0xf853eb8e72…d8401e
Audit this contract →
← previous block·next block →recent activity