← previous blocknext block →recent activity
Analyzing
Block #73,048,130
24 transactions · 20 stateful · 2026-05-07 15:04:54 UTC
Parallelism
71/100
Blocked
50%
Avg conflicts / tx
1.04
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #73,048,130 · 24 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w05w18w09w110w211w312w413w514w616w023w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
14 touches
21 conflicts
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x7f189cf6…afab
0x065c9d…c394
4 touches
1 conflict
0x251861eb…78fd
0x34b655…2a6f
4 touches
1 conflict
0xce7bfe5e…5e58
0x065c9d…c394
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
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: 0xab35264b…1cfa38
21 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity