← previous blocknext block →recent activity
Analyzing
Block #73,375,597
12 transactions · 12 stateful · 2026-05-09 03:23:30 UTC
Parallelism
83/100
Blocked
8%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,375,597 · 12 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
2w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfadb0d6a…e64d
0x34b655…2a6f
4 touches
1 conflict
0x273d80cd…9ecc
0x34b655…2a6f
4 touches
1 conflict
0xedb848fe…6534
0x34b655…2a6f
4 touches
1 conflict
0x1b9e654e…0a08
0x34b655…2a6f
4 touches
1 conflict
0xa91c899f…6ee3
0x34b655…2a6f
4 touches
1 conflict
0x5d70606a…1d53
0x34b655…2a6f
2 touches
0 conflicts
0x61ff022a…dad2
0x34b655…2a6f
2 touches
0 conflicts
0x7cbd466f…1700
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 0xfadb0d6a7a…b4e64d
Audit this contract →
← previous block·next block →recent activity