← previous blocknext block →recent activity
Analyzing
Block #73,673,272
11 transactions · 8 stateful · 2026-05-10 12:28:07 UTC
Parallelism
82/100
Blocked
13%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,673,272 · 11 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
1w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdff247e3…9987
0x34b655…2a6f
4 touches
1 conflict
0x408e66bb…3d6b
0x34b655…2a6f
4 touches
1 conflict
0xa92c8763…6d7f
0x34b655…2a6f
4 touches
1 conflict
0xb91a6f59…722c
0x34b655…2a6f
4 touches
1 conflict
0x0ac31945…2c72
0x065c9d…c394
2 touches
0 conflicts
0x0eee7242…0bf3
0x065c9d…c394
2 touches
0 conflicts
0x15c8b2de…e0ae
0x065c9d…c394
2 touches
0 conflicts
0x1c77168f…f2e1
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 0xdff247e37e…339987
Audit this contract →
← previous block·next block →recent activity