← previous blocknext block →recent activity
Analyzing
Block #73,378,354
8 transactions · 7 stateful · 2026-05-09 03:41:47 UTC
Parallelism
75/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,378,354 · 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
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x070a562a…8147
0x34b655…2a6f
4 touches
1 conflict
0xb81d3ee7…3947
0x34b655…2a6f
4 touches
1 conflict
0xbe2eb1ec…d15a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x22e295f5…1bef
0x065c9d…c394
2 touches
0 conflicts
0x29d417aa…7468
0x065c9d…c394
2 touches
0 conflicts
0x3e1cd845…d52a
0x065c9d…c394
2 touches
0 conflicts
0x4d87512b…897c
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 0x070a562acf…648147
Audit this contract →
← previous block·next block →recent activity