← previous blocknext block →recent activity
Analyzing
Block #73,753,636
8 transactions · 6 stateful · 2026-05-10 21:30:25 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,753,636 · 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
3w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5de96bd3…c60c
0x34b655…2a6f
4 touches
1 conflict
0x8834c319…ef73
0x34b655…2a6f
4 touches
1 conflict
0xfac43f12…b842
0x34b655…2a6f
4 touches
1 conflict
0x2f387761…308c
0x34b655…2a6f
4 touches
1 conflict
0x578e7f66…1b56
0x34b655…2a6f
4 touches
1 conflict
0x21cf1c5d…c310
0xea1b8e…c5ec
2 touches
0 conflicts
0x455b104f…3960
0xea1b8e…c5ec
2 touches
0 conflicts
0xb6b74ae0…8d5e
0xea1b8e…c5ec
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 0x5de96bd34a…ecc60c
Audit this contract →
← previous block·next block →recent activity