← previous blocknext block →recent activity
Analyzing
Block #73,039,106
16 transactions · 13 stateful · 2026-05-07 14:04:48 UTC
Parallelism
81/100
Blocked
31%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,039,106 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w18w09w111w214w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0f9b918b…212d
0x34b655…2a6f
4 touches
1 conflict
0x907226f4…4377
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0xd574ca…7ab1
4 touches
1 conflict
0xf6cc7de8…0b4a
0x3bd359…433a
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x00000000…0003
0x63e48b…53f2
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
3 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity