← previous blocknext block →recent activity
Analyzing
Block #74,771,148
18 transactions · 11 stateful · 2026-05-15 14:39:46 UTC
Parallelism
89/100
Blocked
36%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,771,148 · 18 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
1w02w13w06w110w012w117w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba38536d…2b7d
0x065c9d…c394
4 touches
1 conflict
0xeca21a1d…0146
0x065c9d…c394
4 touches
1 conflict
0x631b4113…baa9
0x34b655…2a6f
4 touches
1 conflict
0xd7143e97…6784
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x420644fc…fcfc
0x065c9d…c394
3 touches
1 conflict
0xb673ae53…aa5a
0x065c9d…c394
3 touches
1 conflict
0x8960e45f…833b
0xd32edf…ff58
3 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: Kuru Exchange: Market-MON/USDC
1 conflict on slot 0xba38536db1…342b7d
Audit this contract →
← previous block·next block →recent activity