← previous blocknext block →recent activity
Analyzing
Block #73,817,120
6 transactions · 6 stateful · 2026-05-11 04:37:31 UTC
Parallelism
67/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,817,120 · 6 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
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1b5d2e60…99b5
0x34b655…2a6f
4 touches
1 conflict
0x80398211…d1cf
0x34b655…2a6f
4 touches
1 conflict
0x899f9688…b4ca
0x34b655…2a6f
4 touches
1 conflict
0xb81d3ee7…3947
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x4d87512b…897c
0x065c9d…c394
2 touches
0 conflicts
0x600e3deb…5a87
0x065c9d…c394
2 touches
0 conflicts
0xb0adc8b8…f6e4
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 0x1b5d2e607a…9999b5
Audit this contract →
← previous block·next block →recent activity