← previous blocknext block →recent activity
Analyzing
Block #74,258,359
9 transactions · 8 stateful · 2026-05-13 05:36:21 UTC
Parallelism
78/100
Blocked
38%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,258,359 · 9 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
1w02w16w07w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2877f440…c2c8
0x34b655…2a6f
4 touches
1 conflict
0x1b5d2e60…99b5
0x34b655…2a6f
4 touches
1 conflict
0x96d74c73…9553
0x34b655…2a6f
4 touches
1 conflict
0x335a161d…fe7f
0x000000…012a
4 touches
1 conflict
0xb9d2cf20…a668
0x34b655…2a6f
4 touches
1 conflict
0x16f33ee9…a797
0x699abc…6a3b
4 touches
1 conflict
0x7e59744a…8354
0x699abc…6a3b
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
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: Perpl
1 conflict on slot 0x2877f4400c…13c2c8
Audit this contract →
← previous block·next block →recent activity