← previous blocknext block →recent activity
Analyzing
Block #74,449,180
26 transactions · 18 stateful · 2026-05-14 02:46:03 UTC
Parallelism
85/100
Blocked
44%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #74,449,180 · 26 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w16w09w010w111w212w317w118w222w023w124w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x17606ba6…1b6e
0x754704…b603
6 touches
3 conflicts
0xf3981be5…2c47
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0xf6cc7de8…0b4a
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0x63e48b…53f2
4 touches
1 conflict
0x00000000…0002
0x63e48b…53f2
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
6 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity